Online Registration Management System (ORMS)

This property is developed under the support of

UNITED INTERNATIONAL UNIVERSITY

Group MembersMd. Rifat UllahI.D:011052001

Group Leader, Analyst and Programmer

Md. Asif-Al-AzadID: 011081008

System Operation Manager

Ahsan AhmadID: 011092026

System Designer and Programmer

Shawana MobashseraID: 011081019

System Manager

Rimon ArefinI.D: 011081016

System Operation Manager

Wahid HossainID: 013073007User manager

Sadia YaminID: 013073008System Manager

CONTENTS IntroductionWork Breakdown ScheduleAnalysisQuestionnairesInterviewFeasibility Analysis

INTRODUCTION And PLANNING Of

ORMSPresented by:Riffat UllahID:011052001Group Leader & Analyst & Programmer

INTRODUCTION At the beginning of developing a system there is a

huge thinking. First of all we have to think that why we want to build a system

Who will be the end user and what ability he carries about operating a system? If any of the system is actively working at present time, what are the bugs and problems that contains. If there is no such system then how the system is manually working on.

From here the concept of System Analysis and Design has arisen

INTRODUCTION (Cont.)According to the concept of System Analysis and Design the total work is divided into 4 to 7 phases. This is called Systems Development Life Cycle. We are using Systems Development Life Cycle with 7 phases. They are:

1. Identifying problems, opportunities, objectives and need.

2. Determining information requirements.3. Analyzing system needs.4. Designing the recommended system.5. Developing and documenting software.6. Test and maintain the system.7. Implementing and evaluating the system.

INTRODUCTION (Cont.)

IDENTIFYING PROBLEMS, OPPORTUNITIES OBJECTIVES AND NEED

At the very beginning of developing of creating a system a company thinks why the need a system or to modify their exiting system. As now we can say that our university is thinking of to modify their existing system as it has some problems. For this reason GROUP One is formed and we the member of the group start IDENTIFYING PROBLEMS, OPPORTUNITIES OBJECTIVES AND NEED. For this we follow the following steps:

1. INITIAL INVESTIGATION2. NEEDs IDENTIFICATION3. DETERMINING THE USER’s INFORMATION Requirements4. CASE SCENARIO5. PROBLEM DEFINATION AND PROJECT INITIATION6. BACKGROUND ANALYSIS7. FACT FINDING8. FACT ANALYSIS9. DETERMINATION OF FEASIBILITY10. WORK BREAKDOWN SCHEDULE

IDENTIFYING PROBLEMS, OPPORTUNITIES OBJECTIVES AND NEED (Cont.)

INITIAL INVESTIGATION

IDENTIFYING PROBLEMS, OPPORTUNITIES OBJECTIVES AND NEED (Cont.)

NEEDs IDENTIFICATION

First we try to find all the shortcomings of the exiting system that makes the system back dated and causes hardship to both of the student and the faculties and think about some new features that may be include in the newer version.

DETERMINING THE USER’s INFORMATION REQUIRMENTs

There are 3 key strategies that use for getting information regarding the user’s requirements:

Asking.Getting Information for the Existing Information System.Prototyping.

We decide to use first two option for obtaining information

IDENTIFYING PROBLEMS, OPPORTUNITIES OBJECTIVES AND NEED (Cont.)

CASE SCENARIO

PROBLEM DEFINATION AND PROJECT INITIATION

To apply the steps undertaken, we use a case based on a real system development project that occurred in our registration system.

Once the project is initiated, the analyst begins to learn about the setting, the existing system, and the physical processes related to the revised system. For example, We are learning our semi automated registration system. How it is working

IDENTIFYING PROBLEMS, OPPORTUNITIES OBJECTIVES AND NEED (Cont.)

BACKGROUND ANALYSIS

FACT FINDING

Once the project is initiated, the analyst begins to learn about the setting, the existing system, and the physical processes related to the revised system.

After obtaining this background knowledge, the analyst begins to collect data on the existing system’s outputs, inputs and costs. The tools used in data collection:- 

Review of written,On-site observations,Interviews,Questionnaires.

IDENTIFYING PROBLEMS, OPPORTUNITIES OBJECTIVES AND NEED (Cont.)

FACT ANALYSIS

DETERMINATION OF FEASIBILITY

As data are collected, they must be organized and evaluated and conclusions drawn for preparing a report to the user for final review and approval. Input/output analysis identifies the elements that are related to the input and outputs of given system. Data flow diagrams enable the analyst to focus on the logic of the system and develop feasible alternatives.

After organizing and summarizing the data, the analyst has a thorough knowledge of the system. The following information should be available:

1. Interview and correspondence records2. Updated system documentation3. Flowcharts4. Familiarity with names, positions, and personalities of user personnel5. Specification of the good and bad features of the current system.6. Understanding of how well actual problems facing the system are in line with the problem(s) stated in the user requested form.

IDENTIFYING PROBLEMS, OPPORTUNITIES OBJECTIVES AND NEED (Cont.)

WORK BREAKDOWN SCHEDULE

To do the full work successfully done it is very important to make a plan – “Who does what?” ”When it has been done?” And so on. That’s why first of all we formed a team called GROUP ONE and selected me: Mr. Rifat Ullah as our team leader. After then we do our first meeting and final everyone’s work schedule. And make work plan as day by day schedule. This is given below:

DETERMINING INFORMATION REQUIRMENTs

Presented by:Wahid HossainID: 013073007User Manager

ONSITE OBSERVATION

First department hang the list of courses which is offers for the next semester on the notice board. And assign students under some faculties. Then these faculties are called Advisor. The student choose the courses from the notice board and go to the advisor for pre-registration.

The advisor checks whether the student complete the pre-requisite of wanting courses and checks conflicts. If any courses need any pre-requisite the advisor advise the student to complete that pre-requisite first. If the pre-requisite completed before, after that the advisor adds the courses in the class schedule of that student for the next semester.

After completing current trimester and publishing the result of the trimester, in a sudden date the advisor asks the student whether he/she wants to make any change in the pre registration, if he/she does not want to change anything, and then he completes the registration.

Definition of Exiting System

ONSITE OBSERVATION (Cont.)

First if schedule has been changed during the gap of pre-registration and registration then some courses can conflict. In this case the advisor tells the student not to take any one of those courses.

Second the capacity of a certain class can cross the limit which is set by the department before the student’s registration is performed.

The last problem which occurs during the registration is, the software checks whether the student has any due, if he/she does, then he/she cannot do registration.

Problems of Exiting System

QUESTIONNAIRE1. How the Application fee/Trimester fee is taken from the students?

2. Are the students having their result through this software?

3. How students register for courses?

4. What if anyone misses the registration’s deadline?

5. What if anyone wants to add/drop/withdraw a course?

6. How students pay fees using the software?

7. How students know about the offered courses?

8. Is the advisor’s authorization needed for the registration?

9. Is student able to change final registration frequently?

10.How the registration process ends?

Feedback Of Interview(Literal representation)

We took interview of 100 students and 5 teachers and they were very happy to hear that our current system will re-construct. They eagerly filled the form.

From their interview we found the new features that to be needed to add. These are:

Payment should be online via bank draft.

Course pre-registration should be free to do at home and so is registration.

Course evaluation should be published in online and so is result with the privacy.

Have the opportunity of adding/dropping/withdrawing courses might do through internet.

Feedback Of Interview(Graphical representation)

QUESTIONNAIRE FOR ADMINISTRATION

Q. 85% students and teachers of 100 students and 5 teachers think paid payment should be online via bank draft and other think payment should be paid physically at university. Which one you prefer most?

Q. 80% students and teachers think course pre-registration should be free to do at home and so is registration And other think it should be do at university manually. What you choose?

Q. 90% students and teachers think course evaluation should be published in online and other think student should come to university to know the course evaluation. Which one you prefer most?

QUESTIONNAIRE FOR ADMINISTRATION

Q. 98% students and teachers think result should be published in online and other think student should come to university to know their result. Which one you prefer most?

Q. 80% students and teachers think student should have the opportunity of adding/dropping/withdrawing courses might do through internet and other think student have to come to the university for adding/dropping/withdrawing courses. Which one you prefer most?

Q. 98% students and teachers think result should be published in online and other think student should come to university to know their result. Which one you prefer most?

FEEDBACK FROM ADMINISTRATION

From their interview with Administration we agree to add some new feature with our new system. These are: 

Course pre-registration should be free to do at home and so is registration.Course evaluation should be published in online and so is result with the privacy.Have the opportunity of adding/dropping/withdrawing courses might do through internet.

ANALYSING SYSTEMNEEDs

Presented by:Shawana MobashseraID:011081019Analyst

FEASIBILITY ANALYSIS

As data collected they must be organized and evaluate and conclusions drawn for preparing a report to the administration for the final review and approval.

To do a feasibility analysis, we need to consider the economic, technical, behavioral and also organizational factors in the system development.

TECHNICAL FEASIBILITYTechnical feasibility centers around the existing computer system (hardware, software, etc.) and to what extent it can support the proposed addition.

For our ongoing system project we have to think two kind of technical feasibility. Such as Hardware feasibility and Software feasibility.

For our System we need hardware having the configuration given below

Hardware Feasibility

Configurations:

Processor: 2.0 GHz or higherMemory: 1 GB RAM or moreHard Disc Space: 3 GB free spaces.

Software Feasibility

The software which we need to develop and deploy the System are mentioned below

Software

NetBeans IDE

Glassfish Server V3

Visual Paradigm for UML 7

Java Runtime Environment 6

Java virtual machine 6

Microsoft Office 07

TECHNICAL FEASIBILITY (Cont.)Though we proposed as, the authority does not agree to permit us to use such components because of limitation of budget. So the authority proposed us to change the requirements like below.

Hardware Feasibility

Configurations:

Processor: 1.8 GHz or higherMemory: 1 GB RAM or moreHard Disc Space: 1 GB free spaces.

Software Feasibility

Software

NetBeans IDE

Glassfish Server V3

StarUML

Java Runtime Environment 6

Java virtual machine 6

LaTeX

TECHNICAL FEASIBILITY (Cont.)

Though they give us such definition. It is not possible to develop that system using this component. So we do a meeting with the authority for fixing this problem. And at the end of the meeting we agree that we can use 2.0 GHz Processor but have to reduce Hard disc Space at 2GB. And at using software components we can use Visual Paradigm for UML 7 but we have to change Microsoft Office 07 as developing software.

ECONOMIC FEASIBILITYFor our proposed system we suggest tentative cost like below:

Name Of component Quantity Cost Net Price

Software 1 piece each mentioned

11,000 taka for Visual Paradigm for UML 7 and 12,000 taka for Microsoft Office 07

23000.00/-

PC At least 3 25,000 each 75000.00/-

Electricity For 4 months 500 taka per working day 15000.00/-

Food and beverage For 4 months 100 taka per person and there works 7 persons

21000.00/-

System deployment and maintenance

50000.00/-

Total 184000.00/-

ECONOMIC FEASIBILITY (Cont.)

Name Of component Quantity Cost Net Price

Software 1 piece each mentioned

11,000 taka for Visual Paradigm for UML 7

11000.00/-

PC At least 3 20,000 each 60000.00/-

Electricity For 4 months 500 taka per working day

15000.00/-

Food and beverage For 4 months 50 taka per person and there works 7 persons

10500.00/-

System deployment and maintenance

50000.00/-

Total 146500.00/-

Though we made that budget for the development of the system but the authority does not support that budget. So another meeting is held for fixing the tentative budget for developing that system. And finally a reduced one is made for developing candidate system. That is like below:

OTHER FEASIBILITY (Cont.)

Behavioral feasibility

Behavioral feasibility analysis is the most important part of a system development. Here we have to conscious about the things of:

1. The old model in which users are habituated.

2. Adding new features that are implemented (not too complex)

Organizational feasibility

Always we have to think about the organization who use the system

DESIGNING The RECOMMANDED

SYSTEM

Presented by:Ahsan AhmedID:011092026System Designer & Programmer

DFD DIAGRAM OF ORMSPROPOSED

DFD DIAGRAM OF ORMSDEPLOYED

UML DIAGRAM OF ORMSPROPOSED

For our System we use four of these diagrams. They are:

1. Use Case Diagram.2. Class Diagram.3. Sequence Diagram.4. Collaboration Diagram.

USE CASE DIAGRAM(PROPOSED)

CLASS DIAGRAM(PROPOSED)

SEQUENCE DIAGRAM(PROPOSED)

COLLOBORETION DIAGRAM(PROPOSED)

UML DIAGRAM OF ORMSDEPLOYED

Though we design the full system but we can not deploy the full system. We here is that part’s UML diagram which we able to deploy. So far we need three diagram for our project.:

1. USE CASE DIAGRAM2. SEQUENCES DIAGRAM3. COLLOBORATION DIAGRAM

USE CASE DIAGRAM(DEPLOYED)

SEQUENCE DIAGRAM(DEPLOYED)

COLLOBORETION DIAGRAM(DEPLOYED)

DEVELOPING & DOCUMENTING THE SYSTEM

Presented by:

Sadia YaminID: 013073008System Manager

REASON FOR TESTING

No program or system design is perfect; communication between the user and the designer is not always complete or clear, and time is usually short.

The first test of system is to see whether it produces the correct outputs. No other test can be more crucial. Following this step, a variety of other tests are conducted:

1. Online response2. Volume3. Stress testing4. Recovery and security5. Usability documentation and procedure

THE TEST PLANE

The first step in system testing is to prepare a plan that will test all aspects of the system in a way that promotes its credibility among potential users. There is psychology in testing:

Programmers usually do better a job in unit testing because they are expected to document and report on the method and extent of their testing.

Users are involved, which means communication is improved between users and the designer group.

Programmers are involved when they become aware of user problems and expectations. The user also becomes more aware of the complexity of programming and testing. The upshot of all this is a more realistic and cooperative user for successful testing.

ACTIVITY NETWORK FOR SYSTEM TESTING

A test plan entails the following activities: 

1. Prepare test plan.2. Specify conditions for users acceptance testing.3. Prepare test data for program testing.4. Prepare test data for transaction path testing.5. Plan user training.6. Compile/assemble programs.7. Prepare job performance aids.8. Prepare operational documents.

PREPARE TEST PLANE

A workable test plan must be prepared in accordance with established design specifications. It includes the following items:

1. Outputs expected from the system.2. Criteria for evaluating outputs.3. A volume of test data.4. Procedure for using test data.5. Personnel and training requirements.

SPACIFYCONDITIONS FORUSER ACCEPTANCE TEATING

Planning for user acceptance testing call for the analyst and the user to agree on the condition for the test. Many of these conditions may be derived from the test plan. Others are agreements on the test schedule, the test duration and the persons designated for the test. The start and termination dates for the test should be specified in advance.

PREPARE TEST DATA FOR PROGRAM TESTING

As each program is coded, test data are prepared and documented to ensure that all aspects of the program are properly tested. After the testing, the data are filed for future reference.

PREPARE TEAT DATA FOR TRANSACTION PATH TESTING

This activity develops the data required for testing every condition and transaction to be introduced into the system. The path of each transaction from origin to destination is carefully tested for reliable results. The test verifies that the test data are virtually comparable to live data used after conversion.

PLANE USEAR TRAINING

User training is designed to prepare the user for testing and converting the system. User involvement and training take place parallel with programming for three reasons: 1. The system group has time available to spend on training while the programs are being written.

2. Initiating a user-training program gives the system group a clearer image of the user’s interest in the new system.

3. A trained user participates more effectively in system testing.

COMPAILE/ ASSEMBLE PROGRAMS

All programs have to be complied / assembled for testing. Before this, however, a complete program description should be available. Included is the purpose of the program, its use, the programmers who prepared it, and the amount of computer time it takes to run it. Program and system flowcharts of the project should also be available for reference.

PREPARE JOB PERFORMANCE ADIS

In this activity the materials to be used by personnel to run the system are specified and scheduled. This include a display of materials such as program codes, a list of input codes attached to the CRT terminal, and a posted instruction schedule to load the desk drive. These aids reduce the training time and employ personnel at lower positions.

PREPARE OPARETIONAL DOCUMENTS

During the test plan stage, all operational documents are finalized, including copies of the operational formats required by the candidate system. Related to operational documentation is a section on the experience, training, and educational qualifications of personnel for the proper operation of the new system.

TESTING AND MAINTAINING THE SYSTEM

Presented by:

Md. Asif-Al-AzadID: 011081008System Operation Manager

PROGRAM(S) TESTING

A program represents the logical elements of a system. For a program to run satisfactorily it must compile and test data correctly and tie in properly with other programs, achieving an error-free program is the responsibility of the programmer. Program testing checks for two types of errors: syntax and logic.

STRING TESTING

Programs are invariably related to one another and interact in total system. Each program is tested to see whether it conforms to related programs in the system. Each portion of the system is tested against the entire module with both test and live data before the entire system is ready to be tested.

SYSTEM TESTING

System testing is designed to uncover weakness that was not found in earlier tests.

This includes forced system failure and validation of the total system as it will be implemented by it user(s) is the operational environment.

Generally, it begins with low volumes of transactions based on live data.

The volume is increased until the maximum level for each transaction type is reached.

SYSTEM DOCUMENTATION

All design and test documentation should be finalized and entered in the library for future reference. The library is the central location for maintenance of the new system. The format, organization, and language of each documentation should be in line with system standards.

USER ACCEPTANCE TESTING

An acceptance test has the objective of selling the user on the validity and reliability of the system. It verifies that the system’s procedures operate to system specifications and that the integrity of vital data is maintained.

Performance of an acceptance test is actually the user’s show. User motivation and knowledge are critical for the successful performance of the system.

Then a comprehensive test report is prepared. The report indicates the system’s tolerance, performance range, error rate, and accuracy.

QUALITY ASSURANCE

Quality assurance defines the objectives of the project and reviews the overall activities so that errors are corrected early in the development process. The software life cycle includes various stages of development, and each stage has the goal of quality assurance.

Quality Factors Specifications1. Correctness2. Reliability3. Efficiency4. Usability5. Maintainability6. Testability7. Portability8. Accuracy9. Error tolerance10. Expandability11. Access control and audit12. Communicativeness

LEVELS OF QUALITY ASSURANCE

There are three levels of quality assurance: testing, validation, and certification:

• System Testing: In system testing, the common view is to eliminate program errors.

• System validation: It checks the quality of the software in both simulated and live environments.

• Certification: Certify that the program or software package is correct and conforms to standards.

IMPLEMENTING AND EVALUATING THE SYSTEM

Presented by:

Rimon ArefinI.D: 011081016System Operation Manager

IMPLEMENTATION

Implementation mean the process of converting a new or a revised system design into an operational system. Conversion is one aspect of implementation. Software maintenance is the post-implementation review.

There are three types of implementation:1. Implementation of a computer system to replace a

manual system.2. Implementation of a new computer system to replace

an existing one.3. Implementation of a modified application to replace an

existing one.

Activity Network for Conversion

1. Conversion begins with a review of the project plan, the system test documentation, and the implementation plan. The parties involved are the user, the project team, programmers, and operations.

2. The conversion portion of the implementation plan is finalized and approved.

3. Files are converted.4. Parallel processing between the existing and the new systems is

initiated.5. Results of computer runs and operations for the new system are

logged on a special form.6. Assuming no problem, parallel processing is discontinued.

Implementation results are documented for reference.7. Conversion is completed. Plans for the post-implementation

review are prepared.

COMBATING RESISTANCE TO CHANGE

Several strategies reduce resistance to system change:1. Identify and discuss the deficiencies of the present

system.2. Do a good, honest job at showing how a changeover

will improve the quality of life at work.3. Establish open communication channels between the

user staff and technical staff to answer questions and fellow up on difficulties after implementation.

4. Invite and use employee participation in all phases of the conversion process.

POST – IMPLEMENTATION REVIEW

• Request for review

• A review plan

1.Administrative plan

2.Personnel requirement plan

3.Hardware plan

4.Documentation review plan

SOFTWARE MAINTANANCE

Maintenance means restoring something to its original condition. Maintenance can be classified as corrective, adaptive, or perfective.

• Corrective maintenance means repairing processing or performance failure or making changes because of previously uncorrected problems.

• Adaptive maintenance means changing the program function.

• Perfective maintenance means enhancing the performance or modifying the program(s) to respond to the user’s additional or changing needs?

PROJECT MANAGEMENT

The process of planning, designing, and implementing computer systems is called a project. Project management is a technique used by a manager to ensure successful completion of a project. It includes the following functions:

• Estimating resource requirement• Scheduling tasks and events• Providing for training and site preparation• Selecting qualified staff and supervising their work• Monitoring the project’s program• Documenting• Periodic evaluating• Contingency planning

Thank You

Save the World-----------------

Use Software For the betterment of HUMAN RACE Not to destroy this world