School Automation

Abstract

  This is a live project which was developed for a local School Management. It is useful to the principal, Admin etc, to maintain the Student details, Teacher Details,

Class’s details. With the help of studentId principal will get total student details as like teacher details also.

  School Automation, which will cover the following modules:

Principal/admin :

Input:  

1)     Enter the student details and update also.

2)     Enter the teacher details and update also.

3)     Enter the class room details also.

Output:

1)     View all the details of the students and teacher.

Steps to start-off the project

1. Study and be comfortable with technologies such as Windows# and SQL server.

2. Understand the specification and come up with any suggestions that could be included.

3. Decide on the strategy or plan or software model to be used.

4. Create flowcharts or DFD’s.

5. Create Database design.

6. Decide on screens with good look and feel.

7. Start on creating the front end and backend.

8. Go module wise in a simple step by step manner rather than rushing on all modules together.

                                                

                                                    System Specifications

Hardware Requirements:-                                                                     Software Requirements: -

Pentium-IV(Processor)                                                                                             Operating System :      Windows

256 MB Ram                                                                                       Programming  language:    C#.NET

512Kb cache memory                                                                                               Web-Technology:     ASP.NET

Hard Disk 10 GB.                                                                                                         Back-End:    SQL SERVER                                                                                                                                                            Microsoft Compatible 101 or more Key Board                                                                      Web Server:      IIS

                                                                                                        

Detail Design

Uml Diagrams

     

                       1 Use Case Diagram

                       2 Class Diagram

                       3  Sequence Diagram

                       4  Collaboration Diagram

                       5  State Chart Diagram

                       6  Activity Diagram

Data Flow Diagram

  

                     1 Context Level Diagram

                     2 First Level DFD

                     3 Second Level DFD

E-R Diagram:-

 Screen Layout:

       

                All Screen Shot Of Web Application

Manpower requirements:

            Project Duration:  90 days ( Business days )

           Project team-size: 4-5

Project Milestones and Schedules :-

No	Milestone Name	Milestone Description	Timeline (No of Days from start of the course)	Remarks
1	Requirements Specification	Complete specification of the system (with appropriate assumptions) . A document detailing the same should be written and a presentation on that be made.	45 days	Attempt should be made to add some more relevant functionalities other than those that are listed in this document. Try t ounderstand the business requirement  and provide solutions.
2	Technology familiarization	Understanding of the technology needed to implement the project.	10 days	The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.
3	Database creation	A database of atleast 10 entries of employees of all grades should be created.	5 days	It is important to finalize on the database at this stage itself so that development and testing  can proceed with the actual database itself.
4	High-level and Detailed  Design	Listing down all possible scenarios like different types of tutorials. Then coming up with flow-charts or pseudocode to handle the scenario.	10 days	The scenarios should map to the requirement specification as well as suggestions on Students part would be invited with concrete reasoning.
5	Implementation of the front-end of the system	Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options.	5 days	During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.
6	Integrating the front-end with the database	The front-end developed in the earlier milestone will now be able to update OTAT database. In short, the system should be ready for integration testing.	5 days
7	Integration Testing	The system should be thoroughly tested by running all the testcases written for the system.	5 days	Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.
8	Final Review	Issues found during the previous milestone are fixed and the system is ready for the final review.	5 days	During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)