Chand and Sons, New Delhi
2. R.S.Aggarwal–“Quantitative Aptitude”, Sultan Chand and Sons, New Delhi
3. Dr.Ravi Chopra – “Verbal and Non–Verbal Reasoning”, MacMillan India
4. Dr.EdwardDeBono – “Lateral Thinking”, Penguin Books, New Delhi
21BSC Project PROJECT WORK Credits: 4 Project work hours 08 Hrs/week
Formative assessment: 40 marks Term end exam:60 marks Project work Exam duration: 03 hrs
The students shall carry out the project work individually under supervision of the course teacher
as allotted by the Chairperson/Principal of the concerned college.
The project work provides an opportunity to design and develop software solution. The student involves
in all the stages of the software development life cycle (SDLC) like, requirements analysis, systems
design, software development/coding, testing and documentation with an overall emphasis on the
development of reliable software systems. The primary emphasis of the project work is to understand and
gain the knowledge of the principles of software engineering practices, and develops good understanding
of SDLC.
Project Topic shall be selected in consultation with the allotted course teacher, The project outcome
should be genuine and original in nature and should not be copied from anywhere else. The project
proposal (synopsis) should include the following details:
1. Title of the Project
2. Objectives of the Project
3. Input to the Project
4. Output of the Project
5. Process Logic (Include a note on the process of arriving from Input to the Output)
6. Tools/Platforms, Languages to be used (Also, mention the reasons for proposing to use them)
7. Details of any Industry/Client if the project chosen is for such Industry/Client.
8. Limitations of the Project and Scope of Future Application.
Following contents shall be reflected in the final project dissertation (documentation). This can be treated
as guidelines for preparing final project documentation.
1. SUMMARY/ABSTRACT
2. Introduction and Objectives
3. Tools/Environment Used
4. Analysis Document (This should include SRS in proper structure based on Software Engineering
concepts, E-R diagrams/Class diagrams/any related diagrams (if the former are not applicable),
Data flow diagrams/other similar diagrams (if the former is not applicable), Data dictionary)
5. Design Document (Modularization details, Data integrity & constraints including database
design, Procedural design, User interface design)
6. Program code (Complete code (well indented)/Detailed specification instead of code*, Comments
& Description. The program code should always be developed in such a way that it includes
complete error handling, passing of parameters as required, placement of procedure/function
12 | B S C - C S 5 & 6 s e m 2 3 - 2 4
statements as needed.)
7. Testing (Test case designs are to be included separately for Unit testing, Integration testing,
System testing; Reports of the outcome of Unit testing, Integration testing, System testing are to
be included separately. Also, details of debugging and code improvement are to be included.)
8. Snapshots of the GUI Screens.
9. Implementation of Security for the Software developed (In case, you have set up a User Name
and Password for your software, you should ensure the security


0 Comments