01-11-2016, 02:36 PM
1463039661-BonafideReport.doc (Size: 952.5 KB / Downloads: 4)
1. INTRODUCTION
1.1 Purpose:
In the fast pace of life the purpose of the project is to design, develop and manage an automatic system for issuing bonafide certificate, which will facilitate all students, faculties and employees of any Institution, so the whole task/process will become more effective, frequent, effortless and standard.
1.2 Scope
In Scope:
• Taking student’s requirement and information as its input which is to be used in certificate.
• Capable of searching and filling all details of student automatically, if his/her data is already stored in database.
• By whom and for whom certificate is generated, all required details are stored for further use.
• Generate certificate automatically by a single click.
• Since it is a computer generated certificate so, there is no requirement of Signature verification.
Out of Scope:
• Unable to work on web.
1.3 Aim
This project is intended to develop an Application to automate the activity of issuing Bonafide certificate. It will be a system which manages whole process by taking user requirement, storing, managing and creating the desired output.
1.4 Objectives
Computerization of present manual system which results in economic use of time and cost.
Instant search functionality.
A certificate is generated via system automatically, which does not need signature of any authorised entities as it is a computer generated report.
All records of students who are issuing certificate are being maintained by this system.
Thus the project aims to improve service of issuing bonafied certificate and automate the whole process.
1.5 Methodologies
Phase 1- Study and Analysis phase
In this phase the basic study of the project is done with step by step analysis.
• Questionnaire is done to know the problem in the current system from users and students.
• Statistical analysis is done on the basis of questionnaire. Some drawbacks were encountered from the analysis.
• Interview of various persons were also taken which includes Mrs. Poonam ma’am.
Phase 2- Design Phase
In this phase the database design of the system is made. The database design is being carried in the following steps:
• Identified the entities and relationships from the scenario.
• Designed ER model for the proposed system and relation among these entities were noted down in the form of tables, having fields as attributes.
• The data flow diagram and the logical model of the system is designed and prepared.
• Physical design of the system is prepared and flow charts are also constructed for each module of the system.
• Defining hardware and software requirements.
Phase 3 – Coding Phase:
• The design of the system is implemented through actual code.
• Proper validation of data is used.
• Proper validation on important fields provided.
Phase 4 - Testing and implementation phase
Testing is done on various test cases and data set. Testing is applied on:
• Testing on each form by taking different user cases.
• Integration of all records of students.
2. Analysis
Software Requirements Specifications (SRS)
1. Introduction
Project Goals and Objectives
Computerization of present manual system which results in economic use of time and cost.
Instant search functionality.
A certificate is generated via system automatically, which does not need signature of any authorised entities as it is a computer generated report.
All records of students who are issuing certificate are being maintained by this system.
Thus the project aims to improve service of issuing bonafied certificate and automate the whole process.
.
1.1. Budget Summary
“No budget required”.
1.2. Project Deliverables
The list of project deliverables is:
• Project Management Plan
• Software Requirements Specification
• Software Design Description
• Software Quality Assurance Plan (including the Software Verification and Validation Plan and the Test Design Document)
• Working System with an Access Database
• Final Studio Document
2. PROJECT ORGANIZATION
2.1. Software Process Models
The systems development life cycle (SDLC), or software development process in systems engineering, information systems and software engineering, is a process of creating or altering information systems, and the models and methodologies that people use to develop these systems. In software engineering, the SDLC concept underpins many kinds of software development methodologies. These methodologies form the framework for planning and controlling the creation of an information system: the software development process.
2.2. Roles and Responsibilities
The software developer is responsible for all documentation to be developed and for all work to be done.
2.2.1. Resources Needed
This project will use resources in the form of time and effort that we will spend developing the project deliverables.
3. Product Overview
3.1. Purpose:
This project is intended to develop an Application to automate the activity of issuing Bonafide certificate. It will be a system which manages whole process by taking user requirement, storing, managing and creating the desired output.
3.2. Scope
3.3. In Scope:
• Taking student’s requirement and information as its input which is to be used in certificate.
• Capable of searching and filling all details of student automatically, if his/her data is already stored in database.
• By whom and for whom certificate is generated, all required details are stored for further use.
• Generate certificate automatically by a single click.
• Since it is a computer generated certificate so, there is no requirement of Signature verification.
Out of Scope:
• Unable to work on web.
3.3 Functional Requirements
3.3.1Inputs and Outputs
• Whenever a student applies for bonafide certificate, system demands the student's specification for it, which will be fulfilled by input via employee.
• Certificate is generated by Jasper i-report.
• Quantities, units of measure, ranges of valid inputs and outputs.
3.3.2 Processing
• Validation of user-id and password.
• Instant Search.
• Any methods (equations or algorithms) to be used to transform inputs to outputs.
3.3.3 Database Requirements
Sqlite3 is used for data storage.
3.4 Non-Functional Requirements
3.5 Software System Attributes
3.5.1 Reliability and Fault Tolerance
The system will have the following backup procedure to ensure system reliability:
• Simultaneous backup in secondary drive.
• Fault tolerance includes details about recovery from failure.
3.5.2 Security
As login name and passwords are used at login time so security is maintained. Some functions are to be kept under control of some specific authority so password protected entry is used.
The additional system security details are as follows:
• Change password verification is implemented.
• Data security should be maintained.
• Unauthorized access to data should be curbed.
• Illegal manipulation of data should be stopped.
3.5.3 Portability
As the size of project code is enormous. So a CD can be used to transfer it from one server to other. If required then data can also be moved using secondary memory devices. So it is portable to a large extent.
3.5.4 Extensibility
The project is easily extensible as website support further editing, such as adding new functions, new plug-in, new forms or editing old forms.
3.5.5 Reusability
The extensibility and portability of this project would make it reusable software.
4. DESIGN
1. Data Flow Diagram
Data flow diagram is a diagram used data flow analysis. Data flow analysis helps systems analysts determine the activities that make up a system, what data are essential to each activity, what data are stored, and what data enter and level the system.
Graphical description of a system’s data and how the processes transform the data is known as Data Flow Diagram.
5. SOFTWARE DEVELOPMENT METHEDOLOGY
Traditional development methodology called system development life cycle methodology, consist of a set of development activities that have a prescribed order. Once a problem or opportunity for a new system is recognized, a request for developing a new system is forwarded for approval. If approved, a study is conducted to ensure that the proposed system is feasible. If feasible, the system requirements are specified followed by phases of systems design, system implementation, testing, conversion and evaluation. A recycling of development activities may occur following system evaluation if system still requires modification or redevelopment. The term 'Development cycle' is used to acknowledge the importance of recycling in meeting information needs.
The system development life cycle is classically thought of as the set of activities that analysts, designers and users carry out to develop and implement an information system. The systems development life cycle consist of following activities:
• Preliminary study / Survey.
• Feasibility study.
• Investigation and fact recording.
• Analysis.
• Design.
• Implementation.
• Maintenance and review.
Let us discuss it one by one.
Preliminary study / Survey
This is the first step of SDLC. This phase is basically concerned about determining whether or not new system should be developed.
During this phase, problems with the current system (manual or automated) are identified. If the benefits seem to outweigh the costs, approval is granted for new projects development. After this the detailed plans and schedules are drafted for making the new system a reality.
During this phase, information should be gathered from many sources. Within the organization, information can be gathered from users, managers, and system developers. Users and managers must be interviewed to find out what exactly they expect from the system. The organizations current capability and operations must be clearly understood so as to use them as inputs to the system. External information is also critical for determining what new systems are available for providing specific types of output. New technologies and developments may allow faster processing, more storage and lower costs than ever before.
Feasibility study
The basic purpose of feasibility study or survey is to determine whether the whole process of systems analysis leading to computerization would be worth the effort for organization. For instance, if an organization is attempting to integrate a number of different computerized systems, the feasibility study might reveal the fact that the integration would not yield desired results and it is better to design the system from the scratch. The feasibility study results in the preparation of a report called the Feasibility Study / Survey Report which is submitted to the management for consideration. It contains the following details:
• A proposed solution to the problem including alternate solutions considered.
• Rough estimates on the cost / benefits analysis if the solution is implemented.
• Approximate time, effort and cost estimates for completion of the project.
System Analysis
System analysis follows the feasibility study. This is the period when the development team collects information from users, management, and data processing personnel regarding the proposed system and the environment in which it will operate, then analyses this information in order to understand, specify, and document requirement specifications. This specification states:
• Goals and objectives of proposed system.
• Fundamental actions that must take place in the software.
• Outputs to be produced.
• Input to be used.
• Processes to be performed.
• Interfaces to be provided.
• Performance requirement to be met.
• Organizational and other constraints to be met.
Tools used in system analysis
As already mentioned, once the information is collected, it must be analyzed for the development team to ascertain user’s needs and write requirement specifications. As a large amount of information is collected, system analysts need tools to record, store and manipulate this information during the analysis process. Various tools are used during analysis. We are going to discuss here a few of them which are quite popular.
3. Flowchart
Flowchart is a graphical representation of an operation or a process. Flowcharting is a graphic technique that is used to represent pictorially the inputs, outputs, and processes of business. In a flowchart, events are represented by various symbols and arrows are used to represent the sequence of events. This technique helps the analyst visualize the parts of system and their relationships. There are number of conventions used in drawing flowcharts. It is very helpful in communicating finding to non technical users.
Graphical representation of an operation or a process is called Flowchart.
4. Process Chart
A process chart is a form which an analyst can fill when studying a process. Each step of the process is listed, the time taken is recorded, and the volume handled is noted. An analysis of the filled chart helps identify duplicate and redundant steps and suggests areas of potential savings in time and effort.
A process chart is a chart enlisting each step of the process along with its activity type, time taken and volume involved.
5. Data Flow Diagram
Data flow diagram is a diagram used data flow analysis. Data flow analysis helps systems analysts determine the activities that make up a system, what data are essential to each activity, what data are stored, and what data enter and level the system.
Graphical description of a system’s data and how the processes transform the data is known as Data Flow Diagram.
6. Decision Table
The decision table is a chat\rt with four sections listing all the logical conditions and actions. In addition the top section permits space for title, date, author, system and comment.
7. Decision Tree
A decision tree, like a decision table, can be used in decision analysis. This technique helps a systems analyst study the relationship of conditions and actions, concepts common to all decisions.
A diagram is drawn that looks like a tree with branches (albeit a horizontal tree), one that relates conditions and actions sequentially. The root of the tree is the starting point of the decision sequence. As you progress along each branch (a condition), decision nodes are encountered. What path to follow from a decision point depends on the sequence of conditions followed.
Maintenance
This stage is the updating and correcting of the program to account for changing conditions or field experience. Proper testing and documentation should significantly reduce the frequency and extent of the required maintenance. Events that cause changes to the original program include:
1. Newly discovered bugs: Errors that are not detected during the original testing phase may be discovered during the actual program operation.
2. Specification changes: The original problem changes because of new laws, user needs, or changing consumer demands. The program must be modified to reflect this change.
3. Specification Expansion: The original program must be expanded to provide additional information that had not been anticipated.
4. New Equipment: The program must be rewritten to take advantage of a new computer or compiler.
7. SYSTEM TESTING
What do we Test for?
The first test of a system is to see whether it produces the correct outputs. Following this step, a variety of other tests are conducted:
1. Online response: Online systems must have a response time that will not cause a hardship to the user.
2. Volume: In this test, we create as many records as would normally be produced to verify that the hardware and software will function correctly.
3. Stress Testing: The purpose of stress testing is to prove that the candidate system does not malfunction under peak loads.
4. Recovery and Security: A forced system failure is induced to test a backup recovery procedure for file integrity. Inaccurate data are entered to see how the system responds in terms of error detection and protection.
5. Usability documentation and procedure: The usability test verifies the user- friendly nature of the system.
Program and Procedure Testing: A program represents the logical elements of a system. Program testing checks for two types of error: syntax and logic. A syntax error is a program statement that violates one or more rules of the language in which it is written. A logic error, on the other hand, deals with incorrect data fields, out- of-range items, and invalid combinations. The diagnostics does not detect logic errors; therefore, the programmer must examine the output carefully for them.
When a program is tested, the actual output is compared with the expected output. When here is a discrepancy, the sequence of instruction must be traced to determine the problem. Procedure testing determines the clarity of documentation on operation and use of system by having users do exactly what manuals request.
CONCLUSION
In the end, after comparing the existing manual system with developed computer system we would conclude that this system of Bonafide certificate automation is totally user friendly and can also be used by a person who has less knowledge about computer.
The system is flexible and can be used by the organization. Great care has been taken to mention each and every operation that taken place in creating bonafide certificate automatically. The system is feasible according to the need of organization.