Online Admission Management System

Transcription

1 IT-Hub College, Sargodha Version: 1.0 Final Project Deliverable Guide Date: Department of Computer Science & Information Technology University of Sargodha Online Admission Management System IT-Hub College, Sargodha. 1

2 IT-Hub College, Sargodha Version: 1.0 Final Project Deliverable Guide Date: Version 1.0 IT-Hub College, Sargodha. 2

3 IT-Hub College, Sargodha Version: 1.0 Final Project Deliverable Guide Date: Table of Contents Chapter 1: Final Project Proposal Introduction Project Title: Project Overview statement: Project Goals & Objectives: High-level system components: List of optional functional units: Exclusions: Application Architecture: Gantt chart: Hardware and Software Specification: Tools and technologies used with reasoning:...11 Chapter 2: First Deliverable Introduction Project/Product Feasibility Report Technical Feasibility Operational Feasibility Economic Feasibility Schedule Feasibility Specification Feasibility Information Feasibility Motivational Feasibility Legal & Ethical Feasibility Project/Product Scope Project/Product Costing Project Cost Estimation by Function Point Analysis Project Cost Estimation by using COCOMO 81 (Constructive Cost Model) Activity Based Costing Task Dependency Table CPM - Critical Path Method Gantt chart Introduction to Team member and their skill set...24 IT-Hub College, Sargodha. 3

4 IT-Hub College, Sargodha Version: 1.0 Final Project Deliverable Guide Date: Task and Member Assignment Table Tools and Technology with reasoning Vision Document Risk List Product Features/ Product Decomposition...29 Chapter 3: Second Deliverable For Object Oriented Approach Introduction: Systems Specifications Identifying External Entities Context Level Data Flow Diagram: Capture "shall" Statements: Allocate Requirements: Prioritize Requirements: Requirements Trace-ability Matrix: Example: Introduction Existing System Scope of the System Summary of Requirements:(Initial Requirements) Identifying External Entities: Capture "shall" Statements: Allocate Requirements: Priorities Requirements: Requirements Traceability Matrix: High Level Usecase Diagram: Analysis Level Usecase Diagram: Usecase Description Chapter 4: Third Deliverable For Object Oriented Approach Introduction: Domain Model System Sequence Diagram Sequence Diagram Defining a Sequence diagram IT-Hub College, Sargodha. 4

5 IT-Hub College, Sargodha Version: 1.0 Final Project Deliverable Guide Date: Basic Sequence Diagram Symbols and Notations Example Distributing Control Flow in Sequence Diagrams Collaboration Diagram Contents of Collaboration Diagrams Constructs of Collaboration Diagram: Operation Contracts Design Class Diagram Create Initial Design Classes Designing Boundary Classes Designing Entity Classes Designing Control Classes Identify Persistent Classes Define Class Visibility Design Class Relationships State chart diagram Data Model...72 Chapter 5: 2nd & 3rd Deliverable For structured Approach Introduction: Entity Relationship Diagram: Data flow diagram (Functional Model) State Transition Diagram Architectural design Component Level Design...87 Chapter 6: 4th Deliverable (User Interface Design) Introduction Site Maps Story boards Navigational maps: Trace-ability Matrix...92 Chapter 7: 5th Deliverable (Software Testing) Introduction: Test plan...95 IT-Hub College, Sargodha. 5

6 IT-Hub College, Sargodha Version: 1.0 Final Project Deliverable Guide Date: Purpose Outline Test design specification Purpose Outline Test Case Specification Purpose Outline Test procedure specification Purpose Outline Test item transmittal report Purpose Outline Test log Purpose Outline Test incident report Purpose Outline Test summary report Purpose Outline Appendixes: Appendix 1: User Interface Introduction Focus on users Integrated with design Early user testing Iterative design Guidelines Appendix 2: Guidelines for Research Projects Appendix 3: Final Documentation Format Guidelines IT-Hub College, Sargodha. 6

7 IT-Hub College, Sargodha Version: 1.0 Final Project Deliverable Guide Date: Appendix 4:Final Documentation Intial Pages Appendix 5: Final Evaluation Matrix for Development Projects Appendix 6: Final Evaluation Matrix for Research Projects Appendix 7: Final Evaluation Matrix for Network Projects Appendix 8: Final Evaluation Metric Appendix 9: Project Registration Form Appendix 11: Evaluation Delay Request Form Appendix 12: Show Cause Form Appendix 13: Project Renrollemnt Form Appendix 14: Change Request Form IT-Hub College, Sargodha. 7

8 Chapter 1: Final Project Proposal 1.1 Project Title: Admission Management System. 1.2 Introduction Admission Management System is aimed at developing an Student Registration application for a College. This system is an online system that can be accessed throughout the organization and outside as well with proper login provided. Our system has two types of accessing modes, administrator and user. Student management system is managed by an administrator. It is the job of the administrator to admit and monitor the whole process. When a user log in to the system, he would only view details of the student. He can't perform any changes.the system has two modules. They are:- Student Administrator Students logging is to apply for the course by filling an application for m provided by online. Administrator logging in may also access/search information put up by the applicants. 1.3 Project Overview Statement Online Admission Management System is intended to be a complete specification of what functionality the admission provides. The main purpose of the system is to automate the task carried out by different peoples in the organization to perform the student admission. Specific design and implementation details will be specified in a future document. Project Overview Statement Project Title: Admission Management System Project Manager: Sir Mehdi Bukhari Project Members: Mehvish Akram, Azeem Ahmad Name Registration # Address Signature Abu Zar 15MIT119 sheikhabzr@live.com Larosh Hammad 15MIT096 laroshhammad777@gmail.com

9 Project Goal: 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 admission Objectives: Sr.# 1 Manage large number of student details. 2 Manage all details of student who registered for the course. 3 Create student accounts and maintain the data s effectively. 4 View all the details of the students. 5 Reduce the work load in interview the students for selection. 6 Activities like updating, modification, deletion of records should be easier. Project Success criteria: Adaptability: The system should be able to adjust to new conditions. Availability: The system ensures 24/7 availability. Reliability: The system functions according to the stated conditions. Response time: The system must have a fast response time. Usability: The system provides ease of use, effectiveness, efficiency, learnability and an overall users satisfaction. In addition, the system will allow users: To Manage large number of student details. To Manage all details of student who registered for the course. To Create student accounts and maintain the data s effectively. To Reduce the work load in interview the students for selection. Activities like updating, modification, deletion of records should be easier.. View all the details of the students. Assumptions, Risks and Obstacles: It is assumed that the team members will cooperate and work seriously on this project. It is assumed that the system would be accessible across all global locations through the Internet. Non availability of the Internet would be one of the major obstacles. It is assumed that the user is familiar with Internet and World Wide Web navigational tools. The users who are not familiar with these tools would face difficulty to use the system. Users will require special training how to use the functionalities of the system. The level of training depends on the role of the users. It is also assumed that administrators/managers will require more training than ordinary users. Willingness, cooperation, and support of all executive level management would be required from requirement engineering to deployment phase. Lack of Willingness, cooperation, and support of all executive level management can lead to an unfinished IT-hub College Sargodha Page 9

10 system. IT infrastructure with proper hardware and high speed Internet connectivity would be required for the effective and successful deployment and running of the system. A slow internet would restrain the accessibility, performance and functioning of the system. Time, technical expertise & budget constrains may introduce serious obstacles towards the completion of the project. Organization Address (if any): Type of project: Research Development Target End users: Development Technology: Object Oriented Structured Platform: Web based Distributed Desktop based Setup Configurations Other Approved By: Date: 1.4 Project Goal & Project Objective: 1.4.1Goal: 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 admission. Some of the goals of the system are listed below: Manage large number of student details. Manage all details of student who registered for the course. Create student accounts and maintain the data s effectively. View all the details of the students. Reduce the work load in interview the students for selection Activities like updating, modification, deletion of records should be easier Objectives: Objective are following: Manage large number of student details. IT-hub College Sargodha Page 10

11 Manage all details of student who registered for the course. Create student accounts and maintain the data s effectively. View all the details of the students. Reduce the work load in interview the students for selection Activities like updating, modification, deletion of records should be easier 1.5 High Level System Components: REGISTRATION & LOGIN SYSTEM: Applicants will carry out their own registration, providing the system with a way to associate a user to their application(s). This will enable the system to display personalized information when the user logs in and certain information, such as name and address, to be added to each application automatically. Giving each student a specific ID will also allow a user to apply to a number of courses, while giving the system a way to prevent unnecessary duplication of applications. Requiring a registration process will also add greater security to the system, as once a user has logged in with their username and password, they will be the only person able to update their information and the only person to make applications on their behalf. 1.6 List of Optional Functional Units Examination System Quiz System 1.7 Exclusions: Whole system can be operated with the help of handheld gadgets and trace any person in the management of the hotel. But the cost of handheld gadget is too much. Voice recognition search which converts voice to text can be extended. But sound processing may take much time for this small level function. 1.8 Applications Architecture: Student Registration Sytem is based on Three Layer Architecture. 1.9 Gantt Chart IT-hub College Sargodha Page 11

12 1.10 Hardware and Software Specification: Hardware: Upto 1.2 Ghz Processor 1GB RAM 20 OR Greater Hard Disk Monitor : VGA/SVGA Software Dream viewer XAMMP 1.10 Tools and Technologies used with reasoning: Tools Adobe Dreamweaver cc 2015: It is easy to use. HTML, CSS, PHP and JavaScript is provided on single platform. Adobe Dreamweaver also have the advantages of less errors. It makes work simpler and easier. Microsoft Office 2016: It provides simple and easily understandable environments. Many tools and designing such as shapes, writing styles is provided there. It can generate the automatic table content. Microsoft Project 2013: It used to make Gantt chart. Gantt chart is a complex diagram which intersect the day, schedule or programs, Microsoft Visio: It used to make different shapes. It is easy to use and easily understandable. It has drag facility which saves a plenty of time Technologies: HTML: HTML is used for front end development. It has predefined tags which functions according to work. The developer does not have to define any tag in this technology. IT-hub College Sargodha Page 12

13 PHP: PHP is faster because it runs in its own memory space. Most tools associated with the program are open source. It is compatible different databases MySql: It is compatible with every operating system. It is open source. It is downloaded and used by the developer with no cost. No client library is needed to compile PHP program. IT-hub College Sargodha Page 13

14 Chapter 2: First Deliverable 2.1 Project/Product Feasibility Report Technical Feasibility Technical feasibility centers on the existing manual system of the test management process and to what extent it can support the system. According to feasibility analysis procedure the technical feasibility of the system is analyzed and the technical requirements such as software facilities, procedure, inputs are identified. It is also one of the important phases of the system development activities. It is technically feasible, since the whole system is designed into the latest technologies like PHP and SQL Server which are the most recent technologies to develop web based systems and design databases. The system offers greater levels of user friendliness combined with greater processing speed. Therefore, the cost of maintenance can be reduced. Since, processing speed is very high and the work is reduced in the maintenance point of view management convince that the project is operationally feasible Operational Feasibility It is Operational feasible, since the system is providing an attractive user interface to the operator/end user, so he feels very easy to work onto it. Response to operator/end user is very fast and very good. Since, as we mentioned above that it requires much less amount of cost, it uses computer work so it is very fast to operate and it is very easy for user to work on it Economic Feasibility Economic analysis is most frequently used for evaluation of the effectiveness of the system. More commonly knows as cost/benefit analysis the procedure is to deter mine the benefit and saving that are expected from a system and compare them with costs, decisions is made to design and implement the system. This part of feasibility study gives the top management the economic justification for the new system. This is an important input to the management the management, because very often the top management does not like to get confounded by the various technicalities that bound to be associated with a project of this kind. A simple economic analysis that gives the actual comparison of costs and benefits is much more meaningful in such cases. It is economically feasible. It will only require a single operator to operate the system, who is responsible for entering the data into the database via a user interface provided to him, who can also able to show all the data in html tabular form so to provide information regarding the students who are either taken admission or to take admission, since it requires only a single person to operate the whole system thus reduces the cost to operate the system. `In the system, the organization is most satisfied by economic feasibility. Because, if the organization implements this system, it need not require any additional hardware resources as well as it will be saving lot of time. IT-hub College Sargodha Page 14

15 Schedule Feasibility This system is developed in almost two month. This project could be divided in sub modules and developed the whole system in a specific time frame. This project is feasible according to the schedule Specification Feasibility This system can almost hold all the features regarding admission management such as Student Registration etc. These all features can be computerized. With the help of this computerized system the student is facilitated quickly. It is only needed the network of some computers, different hardware and some particular users Information Feasibility This system generates meaningful information. This system can hold the information of students. This information is very useful in future. The management can take some serious decision on it Motivational Feasibility This system is useful to serve the students and staff in very well manners. The system can be faster than manual system. We can create student accounts and maintain the data s effectively Legal & Ethical Feasibility This system will be developed in legal environment. All aspects of this system would be legalized Product Scope Without a Admission Management System, managing and maintaining the details of the student is a tedious job for any organization. Student Information system will store all the details of the students including their background information, educational qualifications, personal details and all the information related to their resume. Login module: Login module will help in authentication of user accounts Users who have valid login id and password can only login into their respective accounts. Search module: Suppose there are hundreds of students and from this we have to search a particular student and we know the name of the student.in manual system it is a tedious task though we know the name of the student, but using this module we can easily search the student by specifying the name of the student in the search criteria. Thus this module will help the administrator in searching the student with various criteria easily. Registration Module and Account Management: This module will help the student get registered from anywhere if internet is present.this module will really simplify the task of on paper registration. Also after successful registration the user can update information and change their password as and when required. IT-hub College Sargodha Page 15

16 2.3. Project/Product Costing Product Costing Types Complexity of Components of Components Low Average High Total External Inputs 6x3=18 6x4=24 6x6=36 78 External Outputs 3x4=12 3x5=15 3x7=21 48 External Inquiries 4x3=12 4x4=16 4x6=24 52 Internal logic Files 5x7=35 5x10=50 5x15= External Interface 2x5=10 2x7=14 2x10=20 44 Files Function Point= Value Adjusted Factors * Total unadjusted function points Function Point= 0.9*382 Function Point= 344 Note: Now we know that the complete Function Point for the customer GUI is 344 FPs. Now calculating the efficiency factor, we say that we will complete 8 FP per day that is 43 working days. Productivity parameter=8 FP/per day Labor rate=900/per day Cost / FP = 900 / 8 Total Project Cost = 344 * 200= Total Estimated Effort = 344 /8= 43 Total Number of Unadjusted 382 Function Points Multiplied Value Adjustment Factor 0.5* Total Adjust Function Points 343.8= Project Cost Estimation by using COCOMO MODEL Our application has a medium scope so that it can lies on the o organic domain. Some information about software before we start costing. Total Line of code = 3500(approx.) KLOC = 3.5 Cost per month = 3000/- Basic: Is used mostly for rough, early estimates. Intermediate: Is the most commonly used version, includes 15 different factors to account for the influence of various project attributes such as personnel capability, use of modern tools, hardware constraints, and so forth. IT-hub College Sargodha Page 16

17 Detailed: Accounts for the influence of the different factors on individual project phases: design, coding/testing, and integration/testing. Detailed COCOMO is not used very often. Each level includes three software development types: 1. Organic: Relatively small software teams develop familiar types of software in an in-house environment. Most of the personnel have experience working with related systems. 2. Embedded: The project may require new technology, unfamiliar algorithms, or an innovative new method 3. Semi-detached: Is an intermediate stage between organic and embedded types. Basic COCOMO Type Effort Schedule Organic PM= 2.4 (KLOC)1.05 TD= 2.5(PM)0.38 Semi-Detached PM= 3.0 (KLOC)1.12 TD= 2.5(PM)0.35 Embedded PM= 2.4 (KLOC)1.20 TD= 2.5(PM)0.32 PM= person-month (effort) KLOC= lines of code, in thousands TD= number of months estimated for software development (duration) Intermediate COCOMO Type Organic Semi-Detached Embedded Effort PM= 2.4 (KLOC)1.05 x M PM= 3.0 (KLOC)1.12 x M PM= 2.4 (KLOC)1.20 x M PM= person-month KLOC= lines of code, in thousands M.- reflects 15 predictor variables, called cost drivers The schedule is determined using the Basic COCOMO schedule equations. People Required = Effort / Duration Activity Based Costing Activity-based costing (ABC) is a methodology that measures the cost and performance of activities, resources, and cost objects. Resources are assigned to activities, then activities are assigned to cost objects based on their use. Activity-based costing recognizes the causal relationships of cost drivers to activities. Activity-based costing is about: Measuring business process performance, activity by activity. Estimating the cost of business process outputs based on the cost of the resources used in producing the product. Identifying opportunities to improve process efficiency and effectiveness. IT-hub College Sargodha Page 17

18 Activity costs are used as the quantitative measurement. If activities have unusually high costs or vice versa, they become targets for re-engineering. Activity-based management (ABM) is a broad discipline Basic Cost Drivers: For each activity state in an activity diagram, the basic cost drivers are: Resources: determine what business workers and business entities are participating, and how many instances of each. The allocation of a resource to a workflow implies a certain cost. Cost rate: each business worker or business entity instance may have a cost per time in use. Duration: an activity occurs for a certain time, therefore a resource can either be allocated for the duration of the activity, or for a fixed amount of time. Overhead: any fixed costs that the invocation Effort Time Development Total Cost =2.4(3.5) 1.05 =2.4*3.73 =8.95 PM =2.5(8.95) 0.38 =2.5*2.30 =5.75 M =PM *CM =5.75*3000 =17250/ Task Dependency Table Task ID Task Name Dependency T1 Planning - T2 Investigation T1 T3 Analysis T2 T4 Modeling T1,T2,T3 T5 Prototyping T4 T6 Testing T5 T7 Debugging T4 T8 Final Product All above IT-hub College Sargodha Page 18

19 2.6 CPM Critical Path Method Activity Immediate Predecessor Duration (Days) T1 None 5 T2 T1 20 T3 T2 3 T4 T1,T2,T3 10 T5 T4 5 T6 T5 7 T7 T4 7 T8 All above 15 Network Diagram for the above-mentioned activities 2.7 Gantt Chart IT-hub College Sargodha Page 19

20 2.8 Introduction to Team Member and their Skills set Name Abu Zar (M1) Larosh Hammad (M2) Skill Set PHP MySql HTML CSS PHP MySql HTML CSS 2.9 Task and Member Assignment Table Task Duration (days) Dependencies T1 5 -(M1,M2) T2 20 T1(M1) IT-hub College Sargodha Page 20

21 T3 3 T2(M2) T4 10 T1,T2,T3(M1,M2) T5 5 T4 T6 7 T5(M2) T7 7 T4(M1) T8 15 All above IT-hub College Sargodha Page 21

22 Chapter 3: Second Deliverable For Object Oriented Approach 3.1 Existing System Today in college s student details are entered manually. The student details in separate records are tedious task. Referring to all these records and updating is needed. There is a chance for more manual errors. 1. When the student comes in college. 2. First of all, he/she takes admission form from reception. 3. Fills it and submits it into office. 4. Filled form is first checked with documents like merit list an details came from university and verified by an official person, if there is any mistake then it is corrected. 5. At the time of submission of it the fees is deposited by the candidate. 6. At the time of submission of admission form admission no. is assigned to the candidate by the institute. 7. Candidate gets the receipt of fees deposition. 3.2 Scope of the System The aim of the proposed system is to address the limitations of the current system. The requirements for the system have been gathered from the defects recorded in the past and also based on the feedback from user of previous metrics tools. Following are the objectives of the proposed system: Reach to geographically scattered student:- One of the important objectives of the admission system is communicate with all the students scattered geographically. Reducing time in activities:-reduce the time taken process the applications of students, admitting a student, conducting the online examination, verify student marks, and send call letters to selected students. Centralized data handling:- Transfer the data smoothly to all the departments involved and handle the data centralized way. Paperless admission with reduced manpower:-reduce the manpower needed to perform all admission and administration task by reducing the paper works needed. Cost cutting:- Reduce the cost involved in the admission process. Operational efficiency:-improve the operational efficiency by improving the quality of the process. 3.3 Summary of Requirements: (Initial Requirements) The initial requirement of our system is mentioned below. IT-hub College Sargodha Page 22

23 INPUT REQUIREMENTS REGISTRATION & LOGIN SYSTEM: Applicants will carry out their own registration, providing the system with a way to associate a user to their application(s). This will enable the system to display personalized information when the user logs in and certain information, such as name and address, to be added to each application automatically. Giving each student a specific ID will also allow a user to apply to a number of courses, while giving the system a way to prevent unnecessary duplication of applications. Requiring a registration process will also add greater security to the system, as once a user has logged in with their username and password, they will be the only person able to update their information and the only person to make applications on their behalf. APPLICATION SYSTEM: The application process will be as straightforward as possible, using an intuitive form layout, with the necessary information being completed in stages. The system will monitor this and not allow a student to apply to a single course more than once, but will allow them to apply to multiple courses in the same college. VIEW STATUS: When an application has been completed by a student, they will be able to log in to the system at any time and view its status. UPDATE DETAILS: Applicants will also be able to update their application details. Forms, much like the ones used to register and initially apply, will be the means of inputting the new details and will contain the previous information as a starting point. The only time an application will be locked for editing will be when it has been submitted for admission process that is after date of last submission, after which point the application will no longer be accessible by the user. PROCESSING REQUIREMENTS: The user interface for this system will have to be simple and clear. Most importantly, the pages must be easy to read, easy to understand and accessible. T he color scheme should be appropriate to provide familiarity with the university and there should be no contrast issues. There are many functions the system can perform and these must be logically grouped or displayed in an intuitive order to allow the user to perform tasks quickly and efficiently, without getting lost in excessive amounts of text. The system must also display a large amount of information and to avoid confusion this must be displayed in categories or in different pages. Furthermore, a small amount of information may be displayed initially, for example with a certain limit on date or amount, and the ability to view more in depth information on the subject should be apparent. The different information displays and functionality objects should be individually distinguishable, allowing the user to navigate through recognition, rather than recall In addition, each function must provide the ability to cancel, leaving the user with the ability to rectify mistakes, and every page should include the ability to return to a central location of the system, ensuring that the user does not get lost within IT-hub College Sargodha Page 23

24 the system with no convenient way to navigate. The system will provide different views for different users, allowing multiple access levels. For example, a student will only be able to see their own details and details of their applications, whereas a administrator will be able to view all users, applications and statistics and will have many more privileges. Being an online system, it will naturally be viewable from any computer with an internet connection, allowing admissions from home, for example. This will provide far more accessibility than if it were written in a language with only limited online capability as any computer is a potential work station, rather than relying on the program being installed OUTP UT REQUIREMENTS The most important function is to make the short list of student who got admission under the circumstances made by the college. In some cases, decisions about an application will be simple, given that the application might be exceptionally good or exceptionally bad. If, however, an application is similar to other, previous applications, the tutor may have a more difficult decision to make and inconsistencies may be introduced. Using the automatic ranking of applications a tutor will be able to see a list of applications with a similar ranking. This list will have a default length of 5, for example, but this will be extendible if more comparisons are needed, and the list will include applications of the same rank as well as slightly higher and lower ranks 3.4 Identifying External Entities: Entities: Students Admin 3.5 Capture shall Statement: Para# Initial Requirements 1.0 Shall system be a website? 1.0 Shall system give user interface? 1.0 Shall system give user Registration and log in option too? 1.0 Shall system has a form to enter data for user? 1.0 Shall system have a database? 1.0 Shall system save the data entered by the user? 1.0 Shall system allow admin to register student? IT-hub College Sargodha Page 24

25 3.6 Allocate Requirements: Para# Initial Requirements Use case name 1.0 System shall be a website. Admission Management System 1.0 System shall give user interface. Admission Management System 1.0 System shall give user registration and log in option too. Admission Management System 1.0 System shall has a form to enter data for user. Admission Management System 1.0 System shall have a database. Admission Management System 1.0 System shall save the data entered by the user. Admission Management System 1.0 System shall allow admin to register the student. Admission Management System 1.0 System shall allow admin to manage data of student. Admission Management System 3.7 Priorities Requirements: Para# Rank Initial Requirements 1.0 Highest Will system be a website. 1.0 Highest Will system give user interface. 1.0 Highest Will system give user registration and log in option too. 1.0 Highest Will system has a form to enter data for user. 1.0 Highest Will system has a database. 1.0 Highest Will system save the data entered by the user. Use case ID Uc.1 Uc.1 Uc.1 Uc.1 Uc.1 Uc.1 Use case Name Admission Management System Admission Management System Admission Management System Admission Management System Admission Management System Admission Management System IT-hub College Sargodha Page 25

26 1.0 Highest Will system allow admin to register the student? 3.8 Requirements Traceability Matrix: Uc.1 Admission Management System Sr.No Para no System specification test Build Use case name System will be a website. B1 Admission Management System System will give user interface and log in option too. B1 Admission Management System System will give user registration and log in option too. B1 Admission Management System System will has a form to enter data for user. B2 Admission Management System System will have a database. B2 Admission Management System System will save the data entered by the user. B2 Admission Management System System will allow admin to register the student. B3 Admission Management System System will allow admin to manage data of student. B3 Admission Management System IT-hub College Sargodha Page 26

27 9 1.0 System will allow user to fill form. B3 Admission Management System System will show results of submission of admission form. B3 Admission Management System IT-hub College Sargodha Page 27

28 3.9 High Level Use Case Diagram: IT-hub College Sargodha Page 28

29 3.10 Analysis Level Use Case Diagram IT-hub College Sargodha Page 29

30 Use case Description: 1. Login User Case name : Log In Use cade id : 1 Pre-Conditions : Web page is opened Basic Flow : Enter username and password Alternative Flow : Wrong name or password Post Conditions : Logged In User Case name : Create Profile Use cade id : 2 2. Create Pre-Conditions : Web page is opened Basic Flow : Enter details Profile Alternative Flow : Not Done Post Conditions : Profile created 3. Fill Admission User Case name : Fill admission Use cade id : 3 Form form Pre-Conditions : Web page is opened Basic Flow : Enter personal and academic information Alternative Flow : Not Done Post Conditions : Application submitted User Case name : Manage details Pre-Conditions : Use cade id : 4 Student s information is opened 4. Manage Details IT-hub College Sargodha Page 30

31 Basic Flow : Alternative Flow : Post Conditions : Validate information Eligible or not Validated IT-hub College Sargodha Page 31

32 5. Accept/Reject User Case name : Accept/Reject Use cade id : 5 Pre-Conditions : Checked Student s Information Basic Flow : View personal and academic info of student Alternative Flow : Rejected Post Conditions : Accepted 6. View Status User Case name : View Status Use cade id : 6 Pre-Conditions : Web page is opened Basic Flow : Accepted or rejected Alternative Flow : Not done Post Conditions : Status viewed 7. Make New Admin User Case name : Make New Admin Pre-Conditions : Basic Flow : Alternative Flow : Post Conditions : Use cade id : 7 Web page is opened Assign privileges to someone Not done New admin created 8. Log out User Case name : Log Out Use cade id : 8 Pre-Conditions : Web page is opened Basic Flow : Log out Alternative Flow : Not done Post Conditions : Log out done IT-hub College Sargodha Page 32

33 Object Oriented Approach 4.1 Artifacts which are included in this Chapter: 1. Domain Model 2. User side Sequence Diagram 3. Admin side sequence diagram 4. System sequence diagram 5. Collaboration Diagram 6. Design Class Diagram 7. State Transition Diagram 8. ERD Domain Model: IT-hub College Sargodha Page 33

34 4.1.2 User side Sequence Diagram: IT-hub College Sargodha Page 34

35 4.1.3 Admin side Sequence Diagram: IT-hub College Sargodha Page 35

36 4.1.4 System Sequence Diagram: IT-hub College Sargodha Page 36

37 4.1.5 Collaboration Diagram: IT-hub College Sargodha Page 37

38 4.1.6 Design Class Diagram: IT-hub College Sargodha Page 38

39 4.1.7 State machine Diagram: IT-hub College Sargodha Page 39

40 Chapter 5: 4th Deliverable (User Interface Design) 5.1. Introduction A user interface design consists of three main parts: Page elements should be visualized on paper before building them in the computer. Just as you draw a navigational scheme. 1. Site maps 2. Storyboards 3. Navigational maps 4. Traceability Matrix 5.2. Site Maps: 5.1 Site Map IT-hub College Sargodha Page 40

41 index page: Create New Account: IT-hub College Sargodha Page 41

42 Log In User Admission Form: IT-hub College Sargodha Page 42

43 Upload Documents: My Profile: IT-hub College Sargodha Page 43

44 My Admission Details: IT-hub College Sargodha Page 44

45 Admin Login IT-hub College Sargodha Page 45

46 Admin Panel: : Enter Marks: IT-hub College Sargodha Page 46

47 Add New Manager: IT-hub College Sargodha Page 47

48 Chapter 6: 5 th Deliverable (Software Testing) 6.1Introduction This deliverable is about testing the software. Previous document is related to the interfaces. This deliverable contains the test cases of login, insertion of account, deletion and selection of account Test plans: Fol owing tests are to be performed for testing. There should be no ambiguity about any test methodology or other testing relevant material Login: To login to the software, user ID and password are required, which will be validated from database. If wrong credentials are entered system generates error message. Test Case: Login Test Case ID: 01 Test Enter username and password in the given fields. System will validate the credentials from database and will logion to the system. If wrong username and password are entered system shows the message. Re sults Conclusion Date Passed 1. Constraints were working. 2. User was successfully granted access to system. March,2018 IT-hub College Sargodha Page 48

49 Profile Creation: Test Case: Profile Creation Test Case ID: 02 Test Result To create the account in database, required information for the account is entered in the given fields. If account already exists in database, system generates a message of application otherwise data is inserted successfully. 1. User registered successfully. 2. Constraints were active. Conclusion Passed Date MARCH, Fill Admission Form: Test Case: Fill Admission Form Test case ID : 03 Test Fill the form to apply admission and submit it by user. Result Conclusion Date 1. Constraints are active. 2. Data Insert successfully. Passed March,2018 IT-hub College Sargodha Page 49

50 View Student Form: Test Case: Manage Form By Student Test case ID : 04 Test Student CAN Review the Form and edit the form. Result 1. Constraints are active. 2. From View successfully. 3. Form Edited successfully. Conclusion Date Passed MARCH, Validation of Student Credentials by Admin: Test Case: Validation and View Documents of Students Test case ID : 05 Test Admin can review student data and validate it. Result Conclusion Date Admin successfully view the students data and check for eligibility for Admission Passed March, Students Enrolment APPROVED/Reject by Admin: Test Case: :Admin can Approved or Reject Student. Test case ID : 06 Test Result Click on Aprroved or Reject button Succssfully Accepted or Rejected Students. Conclusion Date Passed March.2018 IT-hub College Sargodha Page 50

51 Enter Marks for entry Exam: Test Case: :Marks enter by Admin Test case ID : 07 Test Enter Marks of Each Students in his/her Record Result Successfully entered marks by Admin Conclusion Date Passed March, News Reading: Test Case: :Add New Admin Test case ID : 08 Test Add New Admin to Database. Result Successfully entered New Admin by admin panel directly to database. Conclusion Date Passed March,2018 IT-hub College Sargodha Page 51

52 IT-hub College Sargodha Page 52

53 Session Msc.IT Project Advisor: Sir Mehdi Bukhari Submitted By Abu Zar Larosh Hammad 15MIT119 15MIT096 IT-Hub College, Sargodha IT-hub College Sargodha Page 53

54 STATEMENT OF SUBMISSION This is certify that Abu Zar Roll No. 15MIT119 and Larosh Hammad Roll No. 15MIT096 successfully completed the final project named as: Online Admission Management System, at the Department of Computer Science & Information Technology, University of Sargodha, to fulfill the requirement of the degree of Msc.Information Technology. Project Supervisor Mehdi Bukhari Project Coordination Office IT-hub College Sargodha Page 54

55 IT-hub College Sargodha Page 55