our school intends to develop a student management system. The system will need
ID: 3577292 • Letter: O
Question
our school intends to develop a student management system. The system will need to hold all details of registered students, including personal information, courses taken, and examination grades. Submit by Day 7 a 3- to 4-page paper that includes the following: A description of the fundamental activities in the software development process. An explanation of the distinction between systems analysis and systems design and a description of the activities involved in each. An explanation of the benefits of information systems. An explanation of what the information system’s requirements are An explanation of why the information system’s requirements are difficult to determine correctly An explanation of why the testing stage of systems development is so important. A description the role of programming, conversion, production, and maintenance in systems development An evaluation of which of the three (programming conversion, production, and maintenance) is most important to project success and why An explanation of which of the three (conversion, production and maintenance) is most difficult to do correctly and why An analysis of the benefits and limitations of each of the following methods of building information systems: traditional waterfall method, prototyping, and component-based development A recommendation for which method the school should use for developing a student management system and justification of your choice
Explanation / Answer
A Student Management System is a system that manages the records of student regarding admission and examination part. It can handle all the details about the student. The details include School details, Course details, Student personal details, Academic Details, Grades details, Courses taken etc. The student management system is an automated version of manual Student Management System. It involves
Manage fees structure
Roll number generation
Fees payment
Admission seat management
Exam scheduling
Result management
Manage new admission
PROBLEM DEFINITION:
The Student Management has to handle records for many number of students and maintenance was difficult. Though it has used an
Information system, it was totally manual. Hence there is a need to upgrade the system with a computer based information system.
EXISTING SYSTEM:
All the details of the student are maintained in a single record. So searching and upgrading the details is a tedious task. Also, there is a chance of errors.
PROPOSED SYSTEM:
By developing the system we can attain the following features:
Easy to handle and feasible
Cost Reduction
Fast and Convenient
PROJECT DESCRIPTION:
The student management system authorized members to access the record of
Academically registered students. It can be used in various educational institutes
across the globe and simplifies working of institutes.
PURPOSE OF THE PROJECT:
This project helps in maintaining the database of the students in any educational organization.
One can easily access any students information anytime and can be kept safely for long period
of time without any damage.
CORE ACTIVITIES PERFORMED:
The entire project development activity is planned according to following steps.
1. Software /Hardware and other necessary for actual development and collected
2. Basic information regarding courses duration cost, eligibility, due.
3. Information modules are prepared.
4. Using above-mentioned methods all modules are integrated.
5. Project prototype thus formed is tested for desired efficiency.
Planning:- The project planning continues by preparing a three stage model viz.
1. Strategic System Planning: - Establishing relationships between real plans for candidate system.
2. Information Requirement Analysis: - Identifying exam requirements to direct the specific application of information at computer institute.
3. Resource Allocation: - Determining Hardware, Software, telecommunication facilities and financial recourses to execute the development of the system.
Benefits of Information System
1. Real Time Data
Through having integrated information in one system, all of the data is up to date. This is essential for all elements of the organization ranging from marketing communications through to finance.
2. Better Communication
Team members will be able to communicate better through having exactly the same information available to them at each time. Its saves having to mis-match data between systems and departments.
3. Reduced Risk of Errors
Due to the fact that data will not have to be replicated, there is less chance of human errors being made which leads to more accurate information available.
4. Greater Productivity
Employees can spend more time on tasks that will help the business to grow, rather than having to replicate data and wait for information to be sent to them from other departments.
5. One Secure Location
Through having all of the necessary data stored in one information system, relevant data is easier for employees to access. Many leading business systems allow restrictions on what individual employees are allowed to access so sensitive information can be seen only by those who need it.
Information System Requirements:
1. Functional requirements:
CREATION OF NEW RECORD: This function creates a record for a new student.
DELETION OF RECORD: This function is used to delete the existing record of any student.
UPDATION IN RECORD: This function updates the information in a record of any student.
DISPLAY OF DATA IN RECORD: This function displays the record of the students.
SEARCHING A RECORD: This function searches a particular record.
2.Non-Functional Requirements:
A) Security:
Only authorized users can access the system with username and password.
B) Performance:
Easy tracking of records and pupation can be done.
C) User Friendly:
The System is very interactive.
D) Maintainability:
Backups for database are available.
Why Information system requirements are difficult to determine:
There can be cases for example if there is only a single student who has opted a course C. If that student leaves the school then his/her information will be deleted from the system. But the course details are also a part of that student record .So they will also be deleted but that course is still available for other students. Such cases create anomalies.
Sometimes the professor/teacher taking a course changes or gets transferred to other department ,or student changes his course .In these cases requirement gathering process becomes difficult.
Why Testing development stage is so important?
A “bug” is really a problem in the code; software testing is focused on finding defects in the finale product. Here are some important defects that better testing would have found.
No system development process will be completed unless the software does exactly what it is supposed to do. Reliability and efficiency are the yardsticks of performance for any software.
Testing will be performed by running the system using the dummy data. It also tested whether the system identifiers the problem correctly. Testing is vital to the success of the system.
System testing makes logical assumption that if all parts of the system are working correctly, the requirements have been satisfied completely. And if requirement have been full filled, the goal can be achieved very easily.
But no system is 100% accurate; there can still be some faults in the system. The testing is done to overcome in maximum number of problem in the system and to make the system bug free.
Difference between 3 stages of testing for an information system:
Software testing has three Main purposes: verification, validation, and defect finding.
The verification process confirms that the software meets its technical specification. A “specification” is a description of a function in terms of a measurable output value given a specific input value specific precondition. A simple specification may be along the time of “a SQL query retrieving data for a single account against the multi-month account account-summery table must return these eight fields <list> ordered by month within 3 second of submission.”
The validation process confirms that the software meets the business requirement. A simple example of business requirement is “after choosing a branch office name, information about the branch customer account managers will appear in a new window. The new window will present manager identification and summery information about each manager’s customer base: <list of data elements.>.” other requirement provides details on how the data will be summarized, formatted and displayed.
A defect is a variance between the expected and actual result. The defects present in the source may be traced to a fault introduced in the specification, design, or development (coding) phases.
ROLE OF PROGRAMMING:
Programming
At this stage of its development, the system is coded, tested, and debugged in a process called programming. Programming is writing instructions for computer execution and testing the written code to ensure that it performs according to specifications. The objective of programming is thus to produce reliable software based on appropriate design specifications.
Programming tasks include:
1. Coding the software module specifications produced during system design into statements in a programming language.
2. Testing at several levels, beginning with testing individual modules as they are programmed and culminating in acceptance or installation testing before the system is placed into operation.
Debugging - problems discovered during testing are tracked down to their source in the code and removed.
To ensure quality of the product, the discipline of structured programming is essential. Coding the program by relying on a small number of simple programming structures for organizing its logic. This makes the program code relatively easy to understand, test, and modify.
ROLE OF CONVERSION:
Conversion: Once You’ve been through the agony of analyzing, designing, programming, and testing and The system meets the requirements, works right, the end users love it, and now the bosses are clamoring to see some results.
There is no right way or wrong way to implement the system; you have to look at it in the context of your particular organization.
You can use the parallel strategy, but it’s expensive to run two separate systems at one time. If you don’t have a lot of confidence in your new system, you might want to go with this one.
If you’re really confident in your development process or if the old system simply doesn’t work anymore, you can use the direct or plunge cutover strategy. For instance, Friday you’re using the old system; on Monday you’re using the new one. This is a high risk approach, but often the least expensive.
If neither of the above describes your organization or your new information system, you might want to consider the phased approach strategy. You can introduce the new system into a single area of the organization. If all goes well there, you can install the new system in other areas. You’re still going to have to figure out how to run two systems at once and also figure out how to integrate the new system with the old system.
ROLE OF PRODUCTION & MAINTAINENCE:
Production and maintenance: You buy a new car and think your problems with the old junker are over. Only for a while. Eventually, you’re going to have to change the oil, buy new tires, get a new air filter. Sooner or later, the new car will become an old car. The same is true with an information system.
After you install the new system and it’s in production, you want to go back one more time and make sure it’s meeting your needs. Eventually you’re going to have to perform maintenance on the system no matter how well you designed and built it. And someday you’ll have to make major changes or replace it altogether.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.