Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

College Management System project

This the Software Engineering Project.

  • Login to see the comments

College Management System project

  1. 1. A PROJECT REPROT ON “AUTOMATION MANAGEMENT SYSTEM” Submitter for the partial fulfillment of the degree Of Bachelor of Technology In COMPUTER SCIENCE Submitted by Manish Kumar Kushwaha And Manish Sharma (RAJDHANI COLLEGE, UNIVERSITY OF DELHI) (NEW DELHI) COMPUTER SCIENCE DEPARTMENT
  2. 2. Certificate This is to certify that the project report entitled “Automation management system” done by Manish Kumar Kushwaha, Roll no. 4155441021 and Manish Sharma, Roll no. 4155441016 under the guidance of Mrs. DIKSHA GROVER, lecturer Rajdhani College, Delhi University. The matter embodied in this project work has not been submitted earlier for the award of any degree to the best of my knowledge and belief. Date: Lecturer Name: Mrs. Diksha Grover Acknowledgement
  3. 3. I would sincerely like to thank for the constructive criticism, support, encouragement, valuable comments, suggestions, timely helps and many innovative ideas given to me by my project supervisor Mrs. Diksha Grover in carrying out the project and the report. I must convey my gratitude to Mrs. Diksha Grover for giving me the constant source of inspiration and help in preparing the project, personally correcting my work and providing encouragement throughout the project. I also thank all my faculty members for steering me through the tough as well as easy phases of the project in result oriented manner with concern attention. Index Table of contents:
  4. 4. I. Problem statement II. ProcessModel III. RequirementAnalysis 1. Information gathering a) Questionnaire b) Interview 2. Software Requirement Specification a) Introduction b) Overall Description c) Specific Requirements 3. Data flow diagram a) Level 0 DFD b) Level 1 DFD c) Level 2 DFD 4. Data Dictionary 5. Use cases IV. Function Points V. Effort Estimation VI. Timeline Chart VII. Risk table VIII. Architectural Design IX. Testing  Basis Path Testing X. Bibliography Problem Statement
  5. 5. Today all works at the time of the admission of the students is done manually by ink and paper, which is very slow and consuming much efforts and time. It is required to design of the computerized Automation Management system, to speed up and make it easy to use system. The present system is the manual one. Hence all the information about the student and faculty details maintained in the files. The whole session attendance is stored in the registers and at the end of the session the report are generated. It becomes very difficult to generate the report in the middle of the session or as per requirement because it takes more time in calculation. At the end of the session the student who don’t have 75% attendance are get a notice. It is unfair to those students if they would have short attendance so that they could take regular classes. The ‘Automation Management System’ software overcomes this problem since the data is stored in computer using DBMS, we can retrieve the record of any student whenever we requires it. It also reduces the manpower needed to perform the entire admission and administration task by reducing the paper works needed.
  6. 6. Process Model The Process Model used in our projects “College Management System” is waterfall model. The Waterfall Model: The waterfall model is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation and Maintenance. The waterfall development model originates in the manufacturing and construction industries: highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development. Diagram: Reasonthe waterfall model inthe software developmentcycle: Since we have well known, clean and fixed requirements therefore it best suits for our software development. Our product definitions is stable. Technology is clearly understood. The project is short. Advantages of the waterfall model: This model is simple and easy to understand and use. In, this model phases are processed and completed one at a time and phases do not overlap. Waterfall model works well for smaller projects where sequence are very well understood.
  7. 7. Disadvantages of the waterfall model: Once an application is in the testing stage, it is very difficult to go back and change something that was not well throughout in the concept stage. High amount of the risk and uncertainty. Poor model for long and ongoing projects.
  8. 8. Questionnaire Q1.Are system requirement allocated to software used to establish a baseline for software engineering and management use? Ans. Yes. Q2.Are estimates (e.g. size, cost, and schedule) documented for use in planning and tracking the software project? Ans. Yes, because the without estimates our software will not developed before the given deadline. Q3.Are software quality assurance (SQA) activities planned? Ans. It is the organizational software so answer is obviously yes to build a good quality software. Q4.Has your organization developed and does it maintain a standard software process? Ans. Yes. Q5.Does your organizational policy allows you to update or modify the software by taking uses feedback? Ans. No. Q6.Are the activities for managing software quality planned for the project? Ans. Yes. Q7.Do the new technology have some effect on quality and productivity? Ans. Obviously Yes, but we are making component based software so any changes can be managed easily. Q8.How much pressure it puts on you to develop a cost effective, reliable software in a limited amount of the time and how you handle this? Ans. Not very much, because we will not include any unnecessary features so that it will be cost effective and developed in given time.
  9. 9. Interview Q1.Do you want restore and backup property in the software? Ans. Yes. Q2.What kinds of the interface you expects from this software? Ans. It should be simple and user friendly. So that a common person or student can operate it easily. Q3.Can you provide any kinds of suggestion toreduce its cost? Ans. If the system works efficiently then, cost doesn’t matter. But yeah you can reduce cost, by not imposing extra taxes and not adding unnecessary features. Q4.Do you want online support in your system or should ewe design it for offline works only? Ans. No, we do want this software to work online. So that student and faculties access it from anywhere. Q5.Do you want this software to work on a specific computing environment? Ans. No, software should work on most of the common operating systems. It should have latest technology
  10. 10. Software Requirements Specification (SRS) I. Introduction Purpose Scope Need for the proposed system II. Overall Description Product Perspective  User Interface  Hardware Interface  Software Interface  Communication Interface  Memory Constraints  Operations  Site Adaption Requirements Product Functions Constraints Assumptions III. Specific Requirements User Class and Characteristics Functional Requirements Performance Requirements Non-Functional Requirements External Interface Requirements  User Interface  Hardware Interface  Software Interface Software System Attributes
  11. 11. Introduction: Today all the work at the time of admission of the students is done manually by ink and paper, which is very, slow and consuming much efforts and time. It is required to Design of Computerized Automated Management System, to speed up and make it easy to use system. It reduces the manpower needed to perform the entire admission and administration task by reducing the paper works needed. The main goal of the systemis to automate the process carried out in the organization with improved performance and realize the vision of paperless work. 1. Purpose: Its purpose is to automate and centralize the whole systemof the department. We are attempting to improve our existing systemthat runs on pen and papers. The main goal of the system is to automate the process carried out in the organization with improved performance and realize the vision of paperless works. 2. Scope: It is more efficient and convenient for the colleges. It reduces the manpower needed to perform the entire administration task by reducing the paper works needed. If all the work is done by the computer there will be no chance of errors. Moreover storing and retrieving of the information is easy, so work can be done speedily and in time. 3. Needfor the proposedsystem: Automation for management system will use the centralized database of the whole systemof the department. Features and Benefits: User friendly Report are easily generated Very less paper works Computer operator control
  12. 12. Overall Description 1) Product Perspective: I. User interface: The application that will be developing will have a user friendly and menu based interface. Following screens will be provided: A login screen for entering the username and passwords, so that the authorized user can have an access without any problems. There will be a screen which will be displaying the major tasks that the system will be performing e.g. add details, delete, view details of the students. All the major tasks mentioned above will have their separate forms and will perform the desired actions. II. Hardware Interface: Intel Pentium 4 or higher processor 1.5Ghz 512MB of RAM or More III. Software Interface: Operating system: Window XP,Vista,7,8,8.1 and higher Platform: .NET Database: SQL server Language: Visual Studio 2013 (ASP.NET & C#) IV. Communication Interface: The communication between the different parts of the system is important they depend on each other. V. Memory Constraints: At least 512MB RAM and 4GB of the Hard disk space will be required for running the application. VI. Operations: The systemwill have the user-friendly interfaces. The system will maintain the records of the students and staff. Only the admin can perform the operations on the databases. User can only see their details or information’s. There will be additional backup for any kind damages or data lost. VII. Site Adaptation Requirements: The centralized database is used so that the systemcan communicate to retrieve the information. 2) Product Function: There will be user name and password to allow access only to authorized users (Admin). The user can take only their information.
  13. 13. Software will perform the following functions: Only the admin can modify the data. Student can only retrieve their information. 3) Constraints: There is a backup for system. GUI feature available. 4) Assumptions: The product require a computer with internet connectivity. The system must be able to respond to the database Software within reasonable time.
  14. 14. Specific Requirements: 1) User class and characteristics: Administrator: The admin keeps tracks of entries of new students to department, entries of new staff to the department, entry of the attendance information etc. Admin can modify the data. User: User can retrieve the information from database by sending the queries. 2) Functional Requirement: The basic service that the automation for management system includes: Entry of the new student to the department. Entry of new staff to the department. Entry of the attendance information. Entry of the examination marks. Provide individual and class-wise report. Update the student profile depending on attendance and exam status. Workloads. System shall provide for password protected administrator access to add, delete and modify the basic service offered by the system. 3) Non-functional Requirement: a) Performance Requirements: The proposed system that we are going to develop will be used as the chief performance system for providing help to the department in managing the whole database of the student studying in the department. Therefore, it is expected that the database would perform functionally all the requirement that are specified. The system should be easy to handle. System should give expected performance results. The response time should be small. b) Security Requirement: We are going to develop a secured database. There are different categories of the users namely administrator, restricted users who will viewing either all or some specific information from the database. Depending upon the category of the user the access rights are decided. It means if the user is an administrator then he can be able to modify the data, append etc. All other user have the rights to retrieve the information about database. c) Safety Requirement: The database may get crashed at any time certain time due to virus or OS failure. Therefore, it is required to take the database backup. 4) External Interface Requirement: a) User Interface: The application that will be developing will have a user friendly and menu based interface.
  15. 15. Following screens will be provided: A loginscreen for entering the user name and password so that the authorized user can have an access to database without any problems. There will be a screen which will be displaying the major tasks that system will be performing i.e. add details, delete, details, view details of the student. All the major tasks mentioned above will have their separate forms and will perform the desired actions. There will be another screen for users for viewing the information. b) Software Interface: Operating system: Window XP,Vista,7,8,8.1 and higher Platform: .NET Database: SQL server Language: Visual Studio 2013 (ASP.NET & C#) c) Hardware Interface: Intel Pentium 4 or higher processor 1.5 GHz 512MB of RAM or More 5) Software System Attributes: The application is easy to interact and communicate with user. This application provides better user interface for ease of working.
  16. 16. Data Flow Diagram (DFD’s) AMS Admin User Report Get info Manage Data Generate Report Details Level 0 DFD
  17. 17. Admin Authentication Login Info Student File Faculty File View Info Generate Report Report User User ID And Password Deleting Entery Remove Editing Entry Modifying Checking ID Removing Enrty Updating Entry Removing Entry Updating Entry Viewing Details Getting Report Details Report Generated Verified Student info Faculty info Viewing student info Viewing Faculty info Level 1DFD
  18. 18. Student Faculty Check Performance Student Performance Check Payment Deatils Fee Payment Details View personal infoStudent Profile View attendance Attendance Working Days Status Faculty Profile View Personal info Working Days Student info View Info Faculty info Checking info Level 2 DFD Student File Viewing Attendance Viewing Profile Viewing Fee Details Viewing info Faculty File Viewing info Details Details Details ViewingProfile Details
  19. 19. Data Dictionary Student info = [Name + Roll No. + D.O.B + Address + Course] Performance = [Internal marks + Assignment Marks | Project marks] Faculty info = [Name + ID No. + D.O.B + Department + Address] Working Days Status = [Total working days + No. of leaves]
  20. 20. Use cases In software engineering, a use case is a list of steps, typically defining interaction between a role (known in Unified modeling language (UML) as an “actor”) and a systemto achieve a goal. In system engineering use cases are used at a higher level that within software engineering, often representing missions or stakeholders goals. Use case 1: Update an entry of the student. Primary Actor: Admin Precondition:Admin has logged in. Main Success Scenario: 1. Admin checks all the previously filled data. 2. Admin retrieve the student data which is meant to update. 3. Admin updated the selected student data from the database. 4. System confirm the modification. Exception Scenario: -2a) There is no such student data, which the searched for.  System shows error message. Function Point Use case 1: Update an entry of the student. Primary Actor: Admin Precondition:Admin has logged in. Main Success Scenario: 1. Admin checks all the previously filled data. 2. Admin retrieve the student data which is meant to update. 3. Admin updated the selected student data from the database. 4. System confirm the modification. Exception Scenario: -2a) There is no such student data, which the searched for.  System shows error message. Use case 2: View Attendance. Primary Actor: User (Student). Precondition: User should be student of that college. Main Success Scenario: 1. Student is asked to fill his roll no. by the software. 2. Now the student’s record displayed on the screen. 3. Student is asked to choose various options (Name, Address, Attendance etc.). 4. Student choose his attendance. 5. Attendance displayed on the screen. Exception Scenario: -1a) Student data is missing.  System shows error message. -5a) The attendance is not up to date.  No error message from software.
  21. 21. Function point (FP) analysis is a structural technique of problem solving. FP is a method to break systeminto small components so that they can better understand and analyzed. Function point analysis is a unique measure for software. Function point can used to  Estimate the cost or effort required to design, code and test the software.  Predict the numbers of the errors that will encountered during the testing.  Forecast the number of component and/or the number of projected source code lines in the implemented system. FP are derived using an empirical relationship based on  Countable (direct) measures of the software’s information domain.  Assessments of the software’s complexity. Information domain values: Number of the External inputs (EIs):  EIs isan elementaryprocessinwhichdatacrossesthe boundaryfromoutside toinside. Thisdata is comingexternal tothe application.The data may come froma data input screenor anotherapplication.The datamaybe usedto maintainone or more internal logical files.The datacanbe eithercontrol informationorbusinessinformation.If the data iscontrol informationitdoesnothave tomaintainaninternal logical file.If an external inputadds,changesanddeletes(maintains) informationonaninternal logical file,thenthisrepresentsthreeexternal inputs. Number of the External outputs (EOs):  EOs an elementaryprocessinwhichderiveddatapassesacrossthe boundaryfrom inside tooutside.Additionally,anEO mayupdate an ILF. The data createsreportsor outputfilessenttootherapplications.These reportsandfilesare createdfrom informationcontainedinone ormore internal logical filesandexternal interface files. Number of the External inquires (EQs):  EQs an elementaryprocesswithbothinputandoutputcomponentsthatresultindata retrieval fromone ormore internal logical filesandexternal interface files.The input processdoesnotupdate or maintainanyFTR’s (Internal Logical FilesorExternal Interface Files)andthe outputside doesnotcontainderiveddata. Number of the Internal logical files (ILFs):  ILs a useridentifiablegroupof logicallyrelateddatathatresidesentirelywithinthe applicationboundaryandismaintainedthroughExternal Inputs.Aninternal logical file has the inherentmeaningitisinternallymaintained,ithassome logical structure andit isstoredin a file. Number of the External interface files (EIFs):  EIFs a useridentifiablegroupof logicallyrelateddatathatis usedforreference purposes only.The data residesentirelyoutsidethe applicationboundaryandismaintainedby anotherapplicationsexternalinputs.The external interface file isaninternal logical file for anotherapplication.
  22. 22. How to calculate the Function Points: Identify/collect the information domain values. Complete the count table to get the count total.  Associate a weighting factor (i.e., complexity value) with each count based on criteria established by the software development organization Evaluate and sum up the adjustment factors. Compute the function point using the following formula: FP = count total*[0.65 + (0.01*∑ (Fi))] Value Adjustment Factors: Rate each factor (Fi, i=1 to14) on a scale of 0 to 5: 1. DOES THE SYSTEM REQUIRE RELIABLEBACKUP ANDRECOVERY? 5 2. ARE SPECIALIZEDDATA COMMUNICATIONSREQUIRED TO TRANSFERINFORMATION TO OR FROMTHE APPLICATION? 3 3. ARE THERE DISTRIBUTED PROCESSINGFUNCTIONS? 0 4. IS PERFORMANCECRITICAL? 3 5. WILL THE SYSTEM IS AN EXISTING, HEAVILY UTILIZED OPERATIONAL ENVIRONMENT? 3 6. DOES THE SYSTEM REQUIRE ONLINEDATA ENTRY? 5 7. DOES THE ONLINEDATA ENTRY REQUIRE THE INPUT TRANSACTION TO BE BUILT OVER MULTIPLE SCREENS OR OPERATIONS? 5 8. ARE THE ILFS UPDATED ONLINE? 4 9. ARE THE INPUTS, OUTPUTS, FILES,OR INQUIRIES COMPLEX? 2 10. IS THE INTERNAL PROCESSINGCOMPLEX? 3 11. IS THE CODE DESIGNED TO BE REUSABLE? 3 12. ARE CONVERSION ANDINSTALLATION INCLUDED IN THEDESIGN? 2 13. IS THE SYSTEM DESIGNED FOR MULTIPLEINSTALLATIONSIN DIFFERENTORGANIZATIONS? 3 14. IS THE APPLICATION DESIGNEDTO FACILITATECHANGEANDEASE OF USE BY THE USER? 4 Total: 45 Calculating FP:
  23. 23. Consider the value of the above question be simple. Weighting Factor Information Domain Values Count Simple Average Complex External Inputs (EIs) 2 x 3 4 6 6 External Outputs (Eos) 1 x 4 5 7 4 External Inquiries (EQs) 6 x 3 4 6 18 Internal Logical Files (ILFs) 2 x 7 10 15 14 External interface Files (EIFs) 2 x 5 7 10 10 Count Total: 52 Since complexity is simple so, ∑ (Fi) = 45, And project FP is 57.2.
  24. 24. Effort Estimation Work effort is the labor required to complete an activity. Work effort is typically the amount of focused an uninterrupted labor time required to compute an activity. FP-based Estimation: Decomposition for FP-based estimation focuses on information domain values rather than software functions. FP estimated =57.2 To derive an estimate of effort on computed FP value, “productivity rate” must be derived. The organizational average productivity rate for system of this type is 6.5 FP/pm. An estimate of the project effort is computed using: Estimated Effort = FP/PROD = 57.2/6.5 = 8.8
  25. 25. Time Line Chart
  26. 26. Risk Table Risks Category Probability Impact Size estimate may be significantly low PS 60% 2 Larger number of the user than planned PS 30% 3 Less reuse than planned PS 70% 2 End-user resist system BU 40% 3 Delivery deadline will be requirements BU 50% 2 Funding will be lost CU 40% 1 Customer will change requirements PS 80% 2 Technology will not meet expectations TE 30% 1 Look of training on tools DE 80% 3 Staff inexperienced ST 30% 2 Staff turnover will be high ST 60% 2
  27. 27. Architectural Design Admin Software User Hardware View info Get infoManage data GenerateReport Admin Login ModifyRemove User ID/ password Editing entryDeleting entry
  28. 28. User View info Generate report View details PrintReport
  29. 29. Basis Path Testing Basis path testing, or structured testing, is a white box method for designing test cases. The method analyzes the control flow graph of a program to find a set of linearly independent paths of execution. The method normally uses cyclomatic complexity to determine the number of linearly independent paths and then generates test cases for each path thus obtained. Basis path testing guarantees complete branch coverage (all CFG edges), but achieves that without covering all possible CFG paths—the latter is usually too costly. Basis path testing has been widely used and studied. To measure the logical complexity of our software we consider the following procedure: void view_info(){ cout<<"Select option: n"; cout<<"1.Student info.n"; cout<<"2.Faculty info. n"; char ch; cin>>ch; if(ch==1){ cout<<"Select option: n"; cout<<"1.Student Profile.n"; cout<<"2.Student Performance.n"; cout<<"3.Attendance.n"; cout<<"4.Fee details.n"; char ch; cin>>ch; if(ch==1){ cout<<"Student Profile: n"; obj.profile(); }else if(ch==2){ cout<<"Student Performance: "; obj.perfrm();
  30. 30. }else if(ch==3){ cout<<"Attendance: "; obj.attendance(); }else{ cout<<"Fee Details: ";; } }else{ cout<<"Select option: n"; cout<<"1.Profilen"; cout<<"2.Working Daysn"; char ch; cin>>ch; if(ch==1){ cout<<"Profile"; obj.profile(); }else{ cout<<"Working Days"; obj.wday(); } } }
  31. 31. Flow Graph of the above procedure: Cyclomatic complexity: Cyclomatic complexity V (G) for a flow graph G is defined as V (G) =E-N+2 1 2 3 4 6 5 78 11 12 1314 15 910
  32. 32. =19-15+2 = 6 So that no. of the independent path is 6. Path 1: 1-2-3-4-5-15 Path 2: 1-2-3-4-6-7-15 Path 3: 1-2-3-4-6-8-9-15 Path 4: 1-2-3-4-6-8-10-15 Path 5: 1-2-11-12-13-15 Path 6: 1-2-11-14-15 Test Cases: Test Scenario Requirements Test cases Test Data Result Check Login Functionality  All correct combinations entered in login/password field will let user in.  All other combinations will be rejected.  Login includes minimum 8 letters and 4 digits/special characters or both (except space character).  Login is not case sensitive.  Password cannot be less than any 8 characters (except space character).  Password is not case sensitive.  “Login in “button is disable unless both fields typed in. Check response on entering valid username and password. Username:mohit0749 Password:temp@123 Login successful Check response on entering invalid username and password. Username: MOHIT Password: temp username is invalid Check response when username and password field is empty and login button is pressed. Username: Password: Username and password invalid
  33. 33. Screen Shots Admin Section: Automation Management System Username: Password: Login Administrator Login Area Automation Management System Faculty Student Enter Student name: 1234 Enter Student Roll No.: XYZ Select Course: None Search Find Cancel
  34. 34. User Section: Automation Management System Attendance PerformanceProfile Fee details Edit Change Photo Remove Name: XYZ Father Name: ABC Mother Name: DEF Course: computer Science Year: Second Roll No.: 1234 Mob. No.: +91-1234567890 Address: New Delhi Details Automation Management System Faculty Student Select Course: All Enter your name: XYZ Enter Your Roll No.: 1234 Submi t Automation Management System Name: XYZ Father Name: ABC Details
  35. 35. Attendance Profile Performance Fee details
  36. 36. Bibliography Books [1] R.S. Pressman, Software Engineering: A Practitioner’s Approach, McGraw-Hill, Ed 7, 2010. [2] P. Jalote, an Integrated Approach to Software Engineering, Narosa PublishingHouse, Edition 3, 2011. Other References [1] [2] [3]