SDTL Mini Project On CENESTO (Central Lab Assessment Software) ACADEMIC YEAR 2011-12 Submitted By Aman Singh Bhandari

Narender Singh Tarun Sharma Vijay Sharma ROLL NO. 3307, 3332, 3358, 3360 Under the guidance of Prof NIKITA GUPTA In partial fulfilment for the award of the degree Of BACHELOR OF COMPUTER ENGINEERING In TE COMPUTER ENGINEERING ARMY INSTITUTE OF TECHNOLOGY DIGHI HILLS, PUNE 411015

CERTIFICATE

This is to certify that the project entitled CENESTO has been carried out by Aman Singh Bhandari, Narender Singh, Tarun Sharma and Vijay Sharma has been carried under my guidance in partial fulfilment of the degree of Bachelor of Engineering in Computer Engineering . To the best of my knowledge and belief this work has not been submitted elsewhere for the award of any other degree

Teacher In-Charge Prof Nikita Gupta

Head of the Department Prof S.R Dhore

TABLE OF CONTENTS 1. 2. Topic CHAPTER ONE: Introduction CHAPTER TWO: Software Requirement Specifications CHAPTER THREE: Analysis Model CHAPTER FOUR: System Design CHAPTER FIVE: Technical Specifications and Implementation 1.0 Over View 2.0 Architecture 3.0 Installation Instructions 4.0 Detailed Design 5.0 Back Up and Recovery CHAPTER SIX: Testing CHAPTER SEVEN: Conclusion and Future Scope REFERENCES Page No. 6 11

3. 4. 5.

13 14 24

6. 7. 8.

24 24 24 25 25 26 34 34

TABLE OF FIGURES
Fig 1. ER Diagrams 2. Analysis Model 3. Screen Shots Page No 8 13 14

ABSTRACT
This project is aimed at developing a LAN based application for the assessment of practicals of the students in the lab. The system is a lan based application that can be accessed throughout the computer department with proper login provided. This system can be used by computer and IT department to reduce the efforts of teachers in assessing the students and make the procedure more transparent. The submitted practicals and the list of assignments can be viewed by the student when he logs in . It also provides students to upload their codes onto the server to be assessed. The teacher can view the uploaded files and assess the students accordingly. The admin is the user who manages the other users and can insert more users and delete the present users or alter them. This a project is an aid to the current state of affairs prevailing in the practical classes.

CHAPTER- ONE INTRODUCTION __________________________________

FEASIBILITY STUDY

RECOGNITION OF NEED:The practicals been conducted now work on the following lines. Students comes for the practicals. He/She performs the practical. The teacher assesses the assignment shown by the student then and there.

FLAWS IN PRESENT WORKING SYSTEM: There are only 2 hours for a teacher to check practicals of 20 students. If a student is not able to complete the assignment on that day, he does not get his incomplete assignment back if by some reason his computer is changed or some one intentionally or unintentionally has deleted his work. The student cannot see all the practicals submitted by him sitting at any computer. The assignments can be submitted without the presence of the teacher.

PROPOSED SOLUTIONS:To develop a system that would accomplish the following: Transparency in assessment criteria. Machine Independence. The assignments are always secure. Teacher can check any time. More efficient use of the machines. Changes pertaining the assignment list can be done easily. Status of any student can be seen any time. Information about which books to be referred.

E-R DIAGRAM

PASSWORD

NAME

LOGIN_ID

LOGIN

LAST_LOGIN_SERIAL

LOG

USER_ID USER_ID TYPE TIME LAST_LOGIN_TIME SUBJECT

TEACH TEACH_ID

USER_ID PRAC_ID STATEMENT UUPID LOCATION

ASSIGNMENT

PRAC_ID

UPLOAD_LOG

SUBMIT_DATE DUE DATE BOOK_REFER TENT_DATE MARKS

COMMENT

1.jsp

login.jsp

student teacher.jsp student.jsp admin.jsp

teacher Modify.jsp Marking.jsp

admin view.jsp add.jsp delete.jsp assess.jsp download.j sp

CHAPTER-TWO SOFTWARE REQUIRMENTS SPECIFICATION __________________________________

1. 1.1 Product Perspective Produce Features This product is a website built using J2EE for Lab assessment in colleges Major features of the website include the following pages/subsections: Users are typical students and the Teacher and the administration of the college The sites run under the local host port 8080 using Apache Tomcat Server.

1.2 User Classes and Characteristics

1.3Operating Environment

1.4Design and Constraints

Implementation Constraints for the website include: Space Bandwidth for storing various information. Renaming of File required before uploading There are no user documents. There are no development assumptions or dependencies.

1.5User Documentation 2.1Assumptions and Dependencies

2.2 Get Real Pages & Sections

Login, home, students, Teacher, news, admin , contact us, army inst. Academics, Marks in Various Assignment are the various sections in the website. 2.3 Exploring Placement Scenarios A listing of the various Assignments given by the teacher and keeping the (existing) track of the Practicals submitted by
10

each student. 2.4Jobs & Money (existing) The monetary expenses incurred were close to negligible. The Web site should work and be tested against IE, Firefox ,Google Chrome Netscape There are no special hardware interface requirements There are no special software interface requirements.Only Various Library in java to be included to run the Upload and download servlet. There are no special communication interface requirements Non- The site should be hosted on a server that can provide adequate response time. The current url being on local host using Apache Tomcat Server 7.0 Copyright and other security measures for the website should be the same as any site. There is a need to track and evaluate the hits and time spent on the student-focused website over time; and make content, design, and navigation changes as needed based on evaluation of hits.

3.1 User Interfaces

3.2 Hardware Interfaces

3.3Software Interfaces

3.4 Communications Interfaces

4.1 Other functionalRequirement: Performance Requirements

4.2 Security Requirements

4.3 Software Quality Attributes .

Web design conventions should be consistent with the standards and conventions used on the site

11

CHAPTER - THREE ANALYSIS MODEL __________________________________

To provide a logical model of a system in terms of classes and relatioonships And how to get things right now and in the future . It includes: 1. 2. 3. 4. 5. 6. Draft the initial class diagram Re examine the behaviour in use cases and objects Refine the class diagram Execute Check Revise Class Diagram Group Releases into Packages
12

INPUT: 1. Uses cases and use case model 2. Problem domain object list.

OUTPUT: 1. Class roles and responsibilities 2. Use case description in terms of classes and operations 3. Completed analysis model ANALYSIS NOTATIONS: 1. 2. 3. 4. 5. 6. Class(rectangle containing name and attributes operations Object(rectangle ) Association (By value/aggregation, cardinality/multiplicity) Generalisation (UML term ) Packages Depends association

13

CHAPTER- FOUR SYSTEM DESIGN __________________________________

The various screen shot describes the system design . The Hardware requirements are already mentioned in the SRS document.

14

15

16

17

18

19

CHAPTER- FIVE TECHNICAL SPECIFICATIONS & IMPLEMENTATION __________________________________

1.0 OVERVIEW

The 1.jsp page is the login page of the website and is seen when website is opened.Depending upon the USER ID and Password the user is given rights as a ADMINISTRATOR a TEACHER or a STUDENT.After successful login each user is directed to their respective homepage . The pages are designed as Java Server pages(JSP). The tool in which the pages are designed is the Dream Weaver and the website simulation is done using Apache Tomcat Server 7.0 2.0 ARCHITECTURE 2.1 System Architecture Computer with Windows 7 2GB RAM, 320 GB HARD DISK Adobe Dream Weaver Apache Tomcat Server 7.0 or Glass Fish or MS IIS Server Java Run Time Environment Java Software Development Kit My Sql Client 5.5 with the Driver for ODBC.(Mysql Connector 5.1) 3.0 INSTALLATION INSTRUCTIONS 3.1 System Configuration Storing all JSP pages need to be stored in the web apps folder of the Apache tomcat server 7.0 And the url will be http://localhost:8080/folder name/jsp page.
20

Data Storage using My Sql software and the ODBC connectivity using MySql Driver 5.1 3.2 System Parameters This includes setting up various system variables . The environment variables are as under. 1. CATALINA_HOME : C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\bin 2. JAVA: C:\Program Files (x86)\Java\jdk1.6.0_18\bin 3. CLASSPATH: C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\lib\servlet-api.jar

4.0 DETAILED DESIGN 4.1 User Interface User Interface is developed using HTML, CSS, XML and DTD .

5.0 BACKUP AND RECOVERY The various data bases : Login Table, Upload log, Marks Assesment , Query, users, User log , Assignment list are stored in a .sql file for flexible use by other users.

21

CHAPTER-SIX TESTING __________________________________

The Checklist The links in the checklist lead to a discussion of each issue. 1. Validation 1. Validate the HTML 2. Validate the CSS 3. Check for broken links 2. Flexibility 1. Try varying window sizes 2. Try varying font sizes 3. Speed 1. Access the site via a modem 2. Check image size specifications 4. Accessibility 1. Test accessibility 2. View in text browser 5. Browser independence 1. Try different browsers 2. Check printed pages 3. Switch JavaScript off 4. Switch plug-ins off 5. Switch images off 6. Other checks 1. Check non-reliance on mailto 2. Check no orphan pages 3. Check sensible page titles

22

Validation Validate the HTML The first stage of checking a web-site is to make sure that you have valid HTML (or XHTML). This can be done with a validator such as the W3C validator or WDG validator. Your own browser may ignore certain errors, but there is a significant risk that markup errors will result in display problems in some browser or other. There are sometimes reasons for including invalid HTML. For example some pages on my own site use the non-standard NOINDEX element, for the benefit of my site search engine. But you should only tolerate HTML validation errors if there is a clear need for the non-standard markup, and if you have tested the result in a variety of browsers. Validate the CSS CSS can be validated with for example the W3C CSS validator. The considerations here are much the same as HTML validation. It may sometimes be necessary to use something non-standard to get Internet Explorer to work, but such rules can be placed in a separate CSS file and hidden in an Internet Explorer conditional comment, where they wont bother other browsers or a validator. Check for broken links Obviously you dont want broken links on your site. There are various tools available to help find these, such as the Link Valet (which is convenient for checking a few pages) or Xenulink (convenient for checking a whole site). Flexibility Try varying window-sizes A very important aspect of web design is coping with different window sizes. Window widths may vary from about 200 pixels on a web-enabled telephone to 2000+ pixels on a technical workstation in full-screen mode. While providing a readable site to the very smallest screens is something of a challenge, your site should at least be readable on a wide variety of sizes. As of mid 2006, nearly 20% of all readers are still using screens of 800x600 pixels or smaller, and if the reader wishes to compare the contents of your site with another document, it is entirely possible that he/she may want to use a window-width of around 400 pixels. Fortunately, at least as far as the text goes, this is not very difficult just refrain from specifying sizes in pixels or points and you are most of the way. See my flexible design page for further thoughts.
23

It is obviously easy to test window-sizes smaller than your own screen-size. Testing larger window-sizes might seem impossible, but you can do a rough simulation using the zoom facility of the Opera browser zoom down to 50% and you get a screen twice the size. It may not be very readable, but any major layout errors should be obvious. Incidentally dont worry too much about the very long lines of text that appear at large screen sizes when small fonts are used. If the reader doesnt use a large font, he can always reduce the window size to something comfortable that is, after all, half the point of having windowing user interfaces in the first place. But if you wish to, you can also use the CSS2 max-width property to limit column width, just as this page does. (Only discerning readers are currently able to benefit from this, as IE does not support it. Rumour has it that it will finally appear in IE 7 I suppose eight years late is better than never.) Try varying font sizes Some people use large screen fonts because they have a large screen with a very fine resolution; other people have to use large screen fonts because of declining eyesight. On the other hand, some people like to use microscopic fonts with their nose pressed against the screen (it takes all sorts...) So while doing the above activity, adjust the default text-size in your browser, and check that all the text scales appropriately. (You did specify the text size in ems or %, didnt you? If not, see my font-size page.) One other aspect to consider is that users may impose a minimum font size to make sure that all text is readable for them. This means that font sizes show a smaller range than you had in mind. If you have a complex page with a wide range of font sizes, it would be worth imposing a minimum size larger than your smallest font (this can be done in e.g. Opera or Firefox) and checking that this does not make parts unreadable. Speed Access the site via a modem So you think you have a great site, full of beautiful images. Put your site on the server then dial in via a modem (a real modem not an ADSL gateway, which is sometimes erroneously referred to as a modem). Does it look so good half a minute later? Or are you still staring at a pretty-much blank screen? If the opening page of your site takes more than about 15 seconds to appear, then you are losing visitors fast. (Broadband users generally expect a still faster response.) Dont overload it. If you have to include large objects on your site perhaps it revolves around high-resolution reproductions of fine art put them on later pages and tell (or warn?) your users what is coming.
24

Web developers usually have broadband access, and they sometimes forget that a large proportion of the world's internet connections still run via a modem. Yes, more and more people are getting broadband, but the number of people without it is still large, and many people in rural areas, let alone developing countries, simply cant yet get broadband. And the growing number of mobile devices frequently have a connection that is less than lightning-fast. By the way, dont make the mistake of assuming that you dont have to worry about bandwidth issues if your site is mainly aimed at companies. I have more than once worked at companies which did have a broadband connection, but had it shared between so many users and applications that the net result was scarcely faster than a dial-up modem. Check image size specifications While doing the test above, check that at least the text of the page appears quickly. If it doesnt (or if it dances all over the place while the page is loading) it is probably because you have forgotten to specify HEIGHT andWIDTH attributes on some of your images. Specifying these enables the browser to work out where the text needs to go, and to display it before the images have finished downloading. Accessibility (for the disabled) Since I first wrote this page, it has been pointed out to me that actually most of the page is about accessibility: that is, ensuring that a web page is accessible under a wide range of browsing conditions. However accessibility is often used in the narrower sense I use in this section. Test accessibility This is mainly important for handicapped users, but also relevant for e.g. people who use a text-only browser, or disable images, because of a slow connection. See the Web Content Accessibility Guidelines. Automated accessibility checking does need to be taken with a largish pinch of salt. Many aspects of the guidelines require human judgement to say whether a page is accessible or not for example whether HTML heading tags are used correctly. And even when the guidelines are unambiguous, you dont need to follow them slavishly. For example the absence of a caption on a table is unimportant if the previous paragraph explained what the table is about. And sometimes checkers even insist on something that isn't actually required by the guidelines. Nonetheless it is well worth running a few pages through a checker such as Cynthia Says or Accessibility in order to familiarise yourself with the issues involved. You can then make the necessary improvements.

25

View in text browser It is also worth running pages through a text-only browser, or text-browser emulator to see what e.g. a blind person using a text-to-speech converter will encounter. It will help you pick up on badly-chosen or missingALT texts for example. It also shows you the site pretty much as a search engine will see it. Incidentally the Opera browser has a built-in text-browser emulator. Browser independence Your site may be viewed in a large variety of situations: different browsers, different operating systems, different features enabled or disabled. It is important that your site stands up well in these different situations. The first point of attention here is validation described separately above. Then there are the following points. Try different browsers Almost all web developers (ahem! perhaps that should read quite a lot of web developers) are aware of the need to check how their site looks in a variety of browsers. How far you go obviously depends on the resources available not everyone is in a position to check Windows, Mac, Unix and Linux platforms. The minimum test would probably be: 1. Firefox, as that has the best standards compliance and is the second mostused browser; 2. Internet Explorer for Windows currently the most widely used browser. It is essential to check both versions 6 and 7 as version 7 fixed quite a lot of bugs in 6 but introduced a new set of its own. (Microsoft is however still kicking developers in the teeth by not making it possible to install both versions on the same computer; you will either need two computers or one of the work-arounds available on the net.) Version 5 should preferably also be checked; as of spring 2008 the number of users is not yet negligible. However it is now uncommon enough that you neednt worry about cosmetic issues; as long as the site is readable that should be sufficient. 3. Opera growing in popularity due to its speed and pretty good standards compliance. For some time I also recommended checking Netscape 4 as well, as it often produces radically different results from any other browser, and was very popular for a long time. However the number of users of this bug-ridden browser is now so small (under 0.1% and decreasing) that it can now probably safely be ignored.

26

Check printed pages Print some of the pages on a normal printer (i.e. with a paper size of A4 or Letter) and check that they appear sensibly. Due to the somewhat limited formatting options available for printing, you probably cant achieve an appearance comparable to a document produced by a word-processor, but you should at least be able to read the text easily, and not have lines running off the right-hand side of the page. It is truly extraordinary how many site authors fail to think of this most elementary of operations. You should also consider using CSS to adjust the appearance of the page when printed. For example you could probably should suppress the printing of information which is not relevant to the printed page, such as navigation bars. This can be done using the @media print or @import print CSS features. Some sites provide separate printer friendly versions of their pages, which the user can select and print. While this may occasionally be necessary as a last resort, it significantly increases the amount of work needed to maintain the site, is inconvenient for the reader and shouldnt usually be needed. Switch Javascript off To run the website correctly javascript should be turned on before using the website Switch plug-ins off The considerations for plug-ins (such as Flash or Java) are very similar to those for Javascript above. Check the site with any plug-ins disabled. The basic text and navigation should still work. Interest the reader sufficiently, and he might just go to the trouble of downloading the plug-in. Greet him with a blank screen or a You need Flash to read this site message and he will probably go away, never to return. Switch images off If scanning a number of sites quickly for information, many readers (including myself) switch images off, for quick loading. Other people cannot view images. So switch images off and check that the site is readable and navigable. This means, in particular, checking that sensible ALT texts have been provided for images. (This check is similar to using a text browser, but not quite the same). Other checks Check non-reliance on mailto In order to give readers a chance to contact them, web authors often include a link of the form mailto:abc@xyz.org. However this unfortunately does not
27

work for anything like all browser/e-mail client combinations. And people in e.g. an Internet cafe cannot use this type of link. Indeed the figure is sometimes circulated that as many as 50% of readers cannot use mailto links. While I doubt whether the true figure is quite this high, it is a substantial number. Many readers prefer a form anyway: most of the responses I get to this site come via the contact form rather than the mailto link. Therefore the best thing is to provide a contact page which has both a mailto link and a contact form; the user can then choose which to use. See my own contact page as an example. Check for orphan pages An orphan page is one that contains no links back up to its ancestors i.e. to pages higher in the hierarchy of the site. Once one arrives at an orphan page, the only way to get to the rest of the site is via the back button. Which is fine until people arrive at the page via a search engine, or via a link that someone else gave to them. They cannot then visit the rest of the site. (True, they may be able to get up the hierarchy by lopping off the end of the URL, but this depends on how the site is built, and is in any case not reader-friendly.) So ensure all pages include a link back up the hierarchy. Orphan pages are particularly easy to overlook in sites with frames. Remember that when one addresses the page directly the other frames are absent. Check sensible page titles Check that the page titles (i.e. the contents of the <TITLE> elements) are sensible. Page titles are important, as for example they show up prominently in search-engine results, in bookmarks and also on the tabs of multi-tab browsers. Generally speaking, each page of a site should have a unique title. They seem to be somewhat prone to the dreaded cut & paste disease. The grep tool is convenient for quickly checking the titles in all your page source files.

28

29

CHAPTER-SEVEN CONCLUSION AND FUTURE SCOPE __________________________________

The website made is a real time replication of lab assessment software in any college . The website includes three different login catering different type of users . Stores their requisite information in a database that can be utilised when required by the user . The website gives an insight to the Teacher about the various practicals carried about by the student, It helps the teacher in marks assessment and various comments can be added to tell the student to improve the project /practicals. Student can Upload various practicals online so that teacher can access the practical whenever and wherever they can even if they are absent.he can see various marks given in the practicals and keep track of various assignment left to submit. We plan to give the website made using Dream Weaver and Java Server Pages to the college and it will surely help the college in a very efficient way . The process of lab assessment can be made very easy and efficient using this software website.

30

REFERENCES
1. 2. 3. 4. Wikipedia.com Java Tutorials on servlets Dream Weaver Catalogue Reverent teachers : Mrs Rushali Patil and Ms Nikita Gupta

31