Project 1
Project 1
In performing our assignment, we were given the help and guideline of our
teachers and seniors to whom we extend our sincere gratitude. We would also like to
thank our professor Mr. Bikram Shah and our guide Mr. Sakar Pathak for giving us
the opportunity to work on this project. It would have never been possible for us to
work at a project without their continuous support and encouragement. We would also
like to expand our deepest gratitude to all those who have directly and indirectly guided
us in this project.
Thanking you
Group members
TABLE OF CONTENTS
1. INTRODUCTION
2. PROBLEM STATEMENT
3. OBJECTIVE
4. SCOPE OF PROJECT
5. REQUREMENT
6. SYSTEM DESIGN
7. IMPLMENTATION
8. TESTING
9. MAINTAINCE AND SUPPORT
10. CONCLUSION
11. REFERENCE
APPENDEX A
APPENDEX B
1.INTRODUCTION
3.Objective
“write about ur main object that why u make ur project”
Functional Requirements:
The system will have following functional requirements
The system will generate a profile based on the information supplied for each
citizen.
The system will allow users to add information to the database based on given
privileges.
Then system will kep all the records in a file so that unauthorized access may
be possible if he/she finds the file.
Non-Functional Requirements:
The system will have following non-functional requirements
● The system will be available all of the time.
● The system will be fast and responsive.
● User interface will be easy and intuitive.
● The system will not do anything that is beyond the privacy policy of the system.
Feasibility Study:
A feasibility study evaluates the project's potential for success; therefore, perceived
objectivity, it is an important factor in the credibility of the study for potential
investors and lending institutions. We, therefore conducted this study with an
objective and with an unbiased approach to provide information upon which decisions
can be based. The Feasibility Studies that are necessary for our system development
are mentioned below:
Technical feasibility:
The game is feasible in a technical manner, a novice can learn the game and turn into
an expert in a matter of hours. Priority was given to intuitive logic during the
development phase but no compromise was done in the efficiency of the code.-edit
this part as same as above
Economic Feasibility :
The system has been made with economical feasibility in mind, the manpower that
was employed to develop this system wasn’t unattainable and the resources needed
for the completion of the project did not budge a hole in anyone’s pocket.
Legal Feasibility :
The game uses the code which is not patented by any other organization, The logic is
very much authentic and the documentation has been done creatively. This implies
that the game is legally feasible and can be legally licensed to anyone for educational
or commercial purpose. –edit this part
Operational Feasibility :
Operational feasibility is the measure of how well a proposed system solves the
problems, and takes advantage of the opportunities identified during scope definition
and how it satisfies the requirements identified in the requirements analysis phase of
system development. After a lot of testing, it was concluded that the game is
technically stable with zero bugs and so, it is not complex to play.-edit this too
Time Management: The Time Management for the project was done by first
allocating a certain workload to all the individuals of the group and then making
predictions on how much time each part of the project will take approximately. After
which, the project got a head start. We took the help of a gantt chart to manage time
efficiently.
SYSTEM DESIGN
1. Conduct the preliminary analysis: in this step, you need to find out the
organization's objectives and the nature and scope of the problem
under study. Even if a problem refers only to a small segment of the
organization itself, you need to find out what the objectives of the
organization itself are. Then you need to see how the problem being
studied fits in with them.
2. Propose alternative solutions: In digging into the organization's
objectives and specific problems, you may have already covered some
solutions. Alternate proposals may come from interviewing employees,
clients, suppliers, and/or consultants. You can also study what
competitors are doing.
Integration and testing: Brings all the pieces together into a special testing
environment, then checks for errors, bugs and interoperability.
Maintenance: During the maintenance stage of the SDLC, the system is assessed
to ensure it does not become obsolete. This is also where changes are made to
initial software. It involves continuous evaluation of the system in terms of its
performance.
Evaluation: Some companies do not view this as an official stage of the SDLC, while
others consider it to be an extension of the maintenance stage, and may be referred to
in some circles as post-implementation review. This is where the system that was
developed, as well as the entire process, is evaluated. Some of the questions that need
to be answered include: does the newly implemented system meet the initial business
requirements and objectives? Is the system reliable and fault-tolerant? Does the system
function according to the approved functional requirements? In addition to evaluating
the software that was released, it is important to assess the effectiveness of the
development process.
If there are any aspects of the entire process, or certain stages, that management is not
satisfied with, this is the time to improve. Evaluation and assessment is a difficult issue.
However, the company must reflect on the process and address weaknesses.
Disposal: In this phase, plans are developed for discarding system information,
hardware and software in making the transition to a new system. The purpose here is to
properly move, archive, discard or destroy information, hardware and software that is
being replaced, in a manner that prevents any possibility of unauthorized disclosure of
sensitive data. The disposal activities ensure proper migration to a new system.
Particular emphasis is given to proper preservation and archival of data processed by
the previous system. All of this should be done in accordance with the organization's
security requirement.
TESTING
IMPLEMENTATION
MAINTAINCE AND SUPPORT
CONCLUSION
REFERENCE
1. BOOK
2. www.wikipedia.org
3. www.technopedia.com
4. www.cplusplus.com
5. www.codewithc.com
APPENDIX A
APPENDIX B
“copy and paste coding of our project”