System Development Project Student Attendance Register System For The Cis Department

SYSTEM
DEVELOPMENT PROJECT
STUDENT ATTENDANCE REGISTER SYSTEM FOR THE CIS DEPARTMENT


SYSTEM DEVELOPMENT PROJECT

Contents
ABSTRACT .................................................................................................................................................................................................... 5
Table 1 Key stages of SDP project ............................................................................................................................................................................................................................................. 6
Stage 1 the richest possible picture of the situation. ...................................................................................................................................... 7
Stage 2 the root definition of the select system and CATWOE. ...................................................................................................................... 9
Root Definition .................................................................................................................................................................................................................................................................................. 9
Table 2 CATWOE and root definition of SAR system .................................................................................................................................................................................................... 11
Stage 3 produces list of functional and non-functional requirement of defined system. .................................................................. 12
Functional Requirements .......................................................................................................................................................................................................................................................... 12
Non-Functional Requirements ................................................................................................................................................................................................................................................ 13
Stage 4 conceptual analysis model of SAR system orders to generated use case with the three narratives .................................................. 15
Table 3 View Attendance History narratives. ................................................................................................................................................................................................................... 17
Table 4 View Override Attendance narratives. ................................................................................................................................................................................................................ 19
Table 5 View Assign Student narratives. ............................................................................................................................................................................................................................ 21
Stage 5 outline possible of smart project plan objective, which include key stakeholders and assumptions in details. ............... 22
SMART objectives ....................................................................................................................................................................................................................................................................... 22
Key stakeholders ......................................................................................................................................................................................................................................................................... 24
Assumption ...................................................................................................................................................................................................................................................................................... 25
Stage 6 Gantt chart action based on stage one to five ................................................................................................................................. 29
Appendix .................................................................................................................................................................................................... 30

2

Figure of content

Figure 1 Rich picture .................................................................................................................................................................................................... 7
Figure 2 Use case of SAR system .......................................................................................................................................................................... 15
Figure 3 List of task name ....................................................................................................................................................................................... 29
Figure 4 Details vies of system scope and software requirements ...................................................................................................... 30
Figure 5 Details view of system deign and testing plan ............................................................................................................................ 31
Figure 6 Details view of training methodology and system documentation .................................................................................... 32
Figure 7 Details view of Pilot, deployment and post implementation review ................................................................................. 33
Figure 8 Timescale and total cost of system scope and software requirements ............................................................................ 34
Figure 9 Timescale and total cost of development, testing and training ........................................................................................... 35
Figure 10 Timescale and total cost of system training and software documentation ................................................................. 36
Figure 11 Timescale and total cost of system pilot, deployment and post implementation ..................................................... 37
Figure 12 Task cost overview ............................................................................................................................................................................... 38
Figure 13 Cost overruns details ........................................................................................................................................................................... 39
Figure 14 Cost overruns, task cost and resource cost variance ............................................................................................................. 40
Figure 15 Cash flow chart ....................................................................................................................................................................................... 41
Figure 16 Work status and over allocation ..................................................................................................................................................... 42
Figure 17 Resource stats and work status ...................................................................................................................................................... 43
Figure 18 Baseline work stats ............................................................................................................................................................................... 44
Figure 19 Resource stats and remaining availability ................................................................................................................................. 45
Figure 20 Milestones due and late tasks completion .................................................................................................................................. 46
3

Figure 21 Cost of status and progress versus cost ....................................................................................................................................... 47

Figure 22 Total hours of labour to build project .......................................................................................................................................... 48
Figure 23 Overall project cost structure table ............................................................................................................................................... 50
Figure 24 Overall project of work and task burn down ............................................................................................................................ 51
Figure 25 Project completed milestones .......................................................................................................................................................... 52
Figure 26 Project slipping tasks ........................................................................................................................................................................... 53
Figure 27 Overall project tasks planning hours ............................................................................................................................................ 54

4

ABSTRACT
The overall aim is project to develop student attendance system for CIS Department by means of both manual
attendance sheet and PDA with an integral barcode reader. Area of system will be concentrated on registration,
lecture attendance by using PDA with an integral barcode reader, record of tutorial and exam attendance, finances,
library access and progression. The university students attendance information is the main facilitates. Course
coordinator, who provided lists of students associated with the course, sorts the information, assign them into one of
multiple lecture occurrences, into smaller tutorial or lab groups and associated to tutors with class rooms or labs.
The main purpose is computerizes PDA with an integral barcode reader and traditional way of taking attendance by
sign in sheet. Major modules of System has:
a. Academic Information System (AIS) team, who have right to updating in subjects (finances and progression), entry
of new faculty, creating spaces for new batch.
b. Academic staff, such as course coordinator, lecturer, tutor and administer as well as student there will be perform
the approved tasks. Following table described step-by-step process and evolution of SAR model of main stages and
emerged.
5

Stage Objective
1 The richest possible picture of the situation.
2 The root definition of the select system and CATWOE.
3 Produces a list of functional and non-functional requirement of the defined system.
4 A conceptual analysis model order to generated use case with the three narratives.
5 Outline possible of smart project plan objective, which include key stakeholders and assumptions.
6 Gantt chart action based on stage one to five.
Table 1 Key stages of SDP project

A rich picture will represent much of SAR system information, which is soft system methodology output of stage 1. A
pictorial description the situation be describe in rich picture under provides focal point and investigation for further
analysis and discussion. It will form and help to develop problem and derive issues, which may appear to be
emerging in the system.
6

Stage 1 the richest possible picture of the situation.

Figure 1 Rich picture
7

The arrow of rich picture signify:

Blue conflict
Green process
Red communication
Black sending data

The Assumption of rich picture:

Some lecture or tutor not happy with latest system, they are very used to with old system. Latest system let
every class to use PDA reader instead of certain class, as it is easy and quick. Two weeks staff training is far too
much; staff can be trained within a week.

Hence University of Greenwich is dealing with oversea student and connection with UKBA, student receive
auto generated warning email or manual from lecturer or tutor once they absent for more than three times in a
month.

8

Stage two the root definition and CATWOE of the select system. The relevant systems need investigation having
established from rich picture. The CATWOE used to define fundamentals of root definition. As starting point
sufficient information will be store at root definition for conceptual model to build.
Stage 2 the root definition of the select system and CATWOE.
Root Definition
The department of Computing and Information System at the University of Greenwich operates an intranet to
support students and staffs a new system of student attendance register (X) through the development of new hybrid
system as develop, design and analysis by developers (Y) for adding alternation, convenient and more precision to
record student attendance (Z).
The following table describe more thoughtful in CATWOE and root definition of system
9

CATWOE element Module Description

Customers 1. Existing student, administration team and CIS staff (lecturer or tutor).
2. Potential student and staff.
Actors 1. Student
2. AIS team
3. CIS staff (tutor or lecturer)
4. Department of computing and information system
5. Vice Chancellor
6. Development team
Transformation Area of system be concentrated on lecture attendance will taking by using PDA with an
integral barcode reader, record of tutorial and exam attendance and print blank register
sheet. The university students attendance information improves the old system and
develops the new attendance system with more functionality.
Weltanschauung Alternative way to develop accurate attendance record system. Also a new way of recoding
World View attendance.
10

Owners The department of Computing and Information System at the University of Greenwich.

Environmental 1. Tight deadline
Constraints 2. Job satisfaction
3. Securing trends
4. Conflicts between Vice Chancellor and CIS department
5. Developer can actually construct the system
Table 2 CATWOE and root definition of SAR system

After successfully established root definition for system stage three required to creating conceptual model, which
described Functional and non-functional requirements that should take place in order to achieve the system to
controlled and monitored.

11

Stage 3 produces list of functional and non-functional requirement of defined system.

Functional Requirements
Dynamically record student attendance and display them, print blank attendance sheet.

Assign students into one of multiple lecture occurrences and into smaller tutorial or lab groups associated to
tutors name and with particular rooms or labs.

Register each of new students in system and keep finances, progression and registration record and maintain
them.

Integral barcode reader should able to uniquely recognize each student in lecture class.
The system should select course and profile.
12

Non-Functional Requirements

Security and access requirements should guarantee, the stakeholder details would not share with third party
organization. All users securely logged on to have benefit from system.

Constraints: organizational constraints are teachable to new and existing member staff within two weeks and easy
operate for academic staff and student. Project constraints are system goes alive within four months, analysis,
design and development budget of 40,000 pounds and no new support posts require. A technical constraint is being
run on existing hardware.

Performance be displaying searching results in less than 60 seconds, multiple transactions using parallel control and
various keywords could use adaptive search engine.
13

All relevant program information and study paths should available 24/7 for enrolled students. The new student
registration formally allow on office hours to prevent any hazardous.
The catalogue of system has access from everyone (lecturer, tutor and student). Secure and private data provide for
enroll student according program access level.
The AIS and lead staff access to every part of system, when accessing system username and password (identification
check) required for all type of users accesses.
Once functional and non-functional requirements had been successfully established stage 4 require to manufacturing
the use case with the three narratives.
14

Stage 4 conceptual analysis model of SAR system orders to generated use case with the three narratives
Figure 2 Use case of SAR system

15

Use case View Attendance History
Brief Description It provide individual attendance records
Actors Student, Faculty lead staff, AIS Team
Precondition User must have valid username and password to pass authentication check for logged
on to web interface.
Main flow 1. User selects to view attendance
2. System displays currently enrolled course list.
3. User selects course to view attendance.
4. System server sends a request to the database to retrieve student information.
5. Database retrieves the information.
6. System server sends the response to the client terminal.
16

Alternative flow 1.User selects to view student profile.
2.System display currently enrolled study path information with hyperlink to view
grades, course schedule and attendant history.
4.User selects course to view attendance.
4. Server sends a request to the database to retrieve student information.
5. Database retrieves the information.
6. System server sends the response to the client terminal.
Post condition Client terminal displays the attendance history with continue or logout option.
Table 3 View Attendance History narratives.

17

Use case Override Attendance
Brief Description It provide user to enter the student attendance onto the system by entering tick next
to each attending students name of particular session.
Actors Academic lead staff
Main flow 1. User selects a subject and date to override attendance Information
2.The system presents the user with the student's current attendance information
3. The user updates the attendance information for the particular subject
4.The system makes the change and records it in audit log and update database.
Alternative flow 1.User selects to view current course information.
2.System display current course information with hyperlink to view student profile,
18

course schedule and attendant history.
4.User selects course to view attendance.
5.Server sends a request to the database to retrieve student attendance.
6.Database retrieves the information.
7.The user updates the attendance information for the student
8.The system makes the change and records it in audit log and update database.
Post condition The system acknowledges whether the requested changes have been made or not.
Table 4 View Override Attendance narratives.

19

Use case Assign Student
Brief Description User maintains lists of students registered on a course; assign them into one of
multiple lecture occurrences and into the smaller tutorial or lab group.
Actors Course Coordinator
Entry Condition The system needs to retrieve lists of students registered on a course data for the user.
Main flow 1. User selects course
2.System presents to user with current course information with hyperlink to updated
particular course information, add new student to exacting course, update classroom,
date and time, assign teacher to exacting course.
20

3. The user select update classroom, date and time.
4.The system presents base on the user selection available room and time for lecture
or smaller for tutorial or lab.
5.User chose vacant room, time and insert to timetable.
6.Systems makes change and records it in audit log and update database.
Post condition The system acknowledges whether the requested changes have been made or not.
Table 5 View Assign Student narratives.

21

Stage 5 outline possible of smart project plan objective, which include key stakeholders and assumptions in
details.
SMART objectives

WEEKLY MEETINGS
The regular weekly meetings with enrol student, Vice Chancellor and lead staff on SAR Project. The meetings
typically are held weekly for at lease 30 minutes at Greenwich campuses or location determined by Vice
Chancellor. The main purpose of meetings is review the planning and development of overall system
implementation and achievement progress, the new SAR system should achieve 90% client satisfaction rating by
end of complied project.

Status reporting
The Vice Chancellor receiving monthly status report by first working day after 15th of each month, reports status
presented according to requirements established in details. The latest system should reduce time taken each
operation process by 40 seconds.
22

System testing
Detailed of test documents is provided and develop in support of system tests and equipment that is performed
on SAR project by 8 March 2016 to Vice Chancellor. The test procedures and test plans contain testing criteria,
activities and management approach for all system testing presented in SAR project plan, aim are major bugs of
system be 0 and there should less than 8 trivial bugs and less than 5 minor bugs at the time of delivery to system
by 3 March 2016.

Program management
The implementation requirements and technology risk areas considered to meet contract specifications within 4
months time periods. The system specification requirements operate by detail benefits and features program
management approach to ensure system delivered 4 months, within 40,000 pounds budget below by 3 March
2016.

23

The about project plan subsections are fit within smart objectives as it described
Specific: It will be base on SAR system for CIS department.
Measurable: It should be complete within the budget of 40 k.
Achievable: It feasible in manageable steps, such as design developing, testing plan, train staff, system
documentation and post implementation review.
Relevant: It is applicable in current economic atmosphere.
Time-bound: It should be complete within 4 months.
Key stakeholders

Primary stakeholders
Academic staff includes course coordinators, lecturers, tutors, they will be using system directly to add attendance of
enrol student, print attendance sheet and view individual attendance records. Student is undergraduate or
postgraduate, they will use system directly to view their program subject and attendance. Administration staff such
as AIS team use system directly to deals centrally with student registration, finances and progression.
24

Secondary Stakeholders
Secondary Stakeholders is Vice Chancellor, who is using system occasionally like verifying system, such as
confirming it up to date for university student used and current industry level.

Tertiary Stakeholders
Tertiary Stakeholders is board of directors, as board of directors will have affected of using it.

Assumption
Student
Student received email send by University of Greenwich team regarding special offers according their preferences by
recording their transactions and search history. Student could unofficially or temporarily register but it not
approved if they have not paid their fees.
25

Chosen system shows whether any PC available in particular campus of specific building with room number as well
as site maps for enroll student. They could view university information, which includes university news, contact
book and directory.
Email send out to new student about registration successfully add or dropped. An important change happens in
course or poor attendance, they are alerted by email send through university lead staff via auto generate report or
manually entering.
Staff
Each staff belongs particular campus, unit and department. Salary dispatch system for current staff to view salary
details in organization. Key stakeholders change their old password to new and edit option for profile. Staff can view
staff profile, search other staff profile or student profile. Accessibility predefined to secure access of private users
details, so all type users within system not to accessible all part of data.

26

System
It provide student auditable records of six years after completed applicable audits and redundancy procedures,
backup. Each individual PCs current data should be automatic backups.
Support shared platform information, sharing between staff based in different university campus. Encourage
primary stakeholders provide feedback about quality of system and service of web.
Due to over approach or access at same time, system could freeze or disconnect. It locks that abnormal process made
up to point and user data save in secure catalog. All data and work provided when user sign in back with same user
Id.
Integral barcode reader have skill to display meaning full message with students Id, name with photo. It present
access denied or approved message to express student and play alert sounds for their attendance failures or
successes. This is conclusion of assumption following session include fundamentals of advantages and disadvantages
of chosen system.
27

Advantages:
User friendly, non-intrusive, acceptable in high sociality
Auto reports system is easily generated, less time in verification.
Very less technology cost and paper work.
Accurate results in PDA barcode reader

Disadvantages
There are possibilities of frauds.
Less sophisticated methods used.
Authentication is difficult or impossible for a cracked or dirt card of barcode reader.
This is termination of advantages and disadvantages following session include feature of Gantt chart and essentials.
28

Stage 6 Gantt chart action based on stage one to five

Figure 3 list of task name

29

Appendix
Following section is various screenshot of Gantt chart details
Figure 4 Details vies of system scope and software requirements
30

Figure 5 Details view of system deign and testing plan
31

Figure 6 Details view of training methodology and system documentation
32

Figure 7 Details view of Pilot, deployment and post implementation review

33

Figure 8 Timescale and total cost of system scope and software requirements

34

Figure 9 Timescale and total cost of development, testing and training

35

Figure 10 Timescale and total cost of system training and software documentation

36

Figure 11 Timescale and total cost of system pilot, deployment and post implementation
The following session of appendix will demonstrate project plan details of chosen system in table and chart.
37

Figure 12 Task cost overview
38

Figure 13 Cost overruns details
39

Figure 14 Cost overruns, task cost and resource cost variance
40

Figure 15 Cash flow chart
41

Figure 16 Work status and over allocation
42

Figure 17 Resource stats and work status
43

Figure 18 Baseline work stats
44

Figure 19 Resource stats and remaining availability
45

Figure 20 Milestones due and late tasks completion
46

Figure 21 Cost of status and progress versus cost
47

Figure 22 Total hours of labour to build project
48

Name Actual Cost Remaining Baseline Cost Cost
Cost Cost Variance
1 System scope 3,275.35 37.65 0.00 3,313.00 3,313.00

2Software 8,266.04 363.96 0.00 8,630.00 8,630.00

Requirements
3 Design 10,730.53 652.47 0.00 11,383.00 11,383.00
4 Testing plan 2,910.24 41.76 0.00 2,952.00 2,952.00
5 Training 5,079.34 985.66 0.00 6,065.00 6,065.00
6System 7,689.88 272.12 0.00 7,962.00 7,962.00

documentation
49

7 Pilot 2,843.12 92.88 0.00 2,936.00 2,936.00

8 Deployment 2,545.60 51.40 0.00 2,597.00 2,597.00

9 Post 2,244.78 26.22 0.00 2,271.00 2,271.00
Implementation
Review
SAR system 0.00 0.00 0.00 0.00 0.00
development
complete

Figure 23 Overall project cost structure table

50

Figure 24 Overall project of work and task burn down
51

Figure 25 Project completed milestones
52

Figure 26 Project slipping tasks
53

Figure 27 Overall project tasks planning hours
End of Appendix
54

System Development Project Student Attendance Register System For The Cis Department

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

System Development Project Student Attendance Register System For The Cis Department

Transféré par

Droits d'auteur :

Formats disponibles

SYSTEM

Figure 21 Cost of status and progress versus cost ....................................................................................................................................... 47

1 The richest possible picture of the situation.

2 The root definition of the select system and CATWOE.

3 Produces a list of functional and non-functional requirement of the defined system.

6 Gantt chart action based on stage one to five.

Table 1 Key stages of SDP project

Stage 1 the richest possible picture of the situation.

Stage 2 the root definition of the select system and CATWOE.

CATWOE element Module Description

Table 2 CATWOE and root definition of SAR system

Stage 3 produces list of functional and non-functional requirement of defined system.

The system should select course and profile.

Figure 2 Use case of SAR system

Use case View Attendance History

Brief Description It provide individual attendance records

Actors Student, Faculty lead staff, AIS Team

Main flow 1. User selects to view attendance

2. System displays currently enrolled course list.

3. User selects course to view attendance.

4. System server sends a request to the database to retrieve student information.

5. Database retrieves the information.

6. System server sends the response to the client terminal.

Alternative flow 1.User selects to view student profile.

4.User selects course to view attendance.

4. Server sends a request to the database to retrieve student information.

5. Database retrieves the information.

6. System server sends the response to the client terminal.

Table 3 View Attendance History narratives.

Use case Override Attendance

Actors Academic lead staff

Alternative flow 1.User selects to view current course information.

course schedule and attendant history.

4.User selects course to view attendance.

5.Server sends a request to the database to retrieve student attendance.

6.Database retrieves the information.

7.The user updates the attendance information for the student

Table 4 View Override Attendance narratives.

Actors Course Coordinator

Main flow 1. User selects course

3. The user select update classroom, date and time.

5.User chose vacant room, time and insert to timetable.

Table 5 View Assign Student narratives.

Less sophisticated methods used.

Authentication is difficult or impossible for a cracked or dirt card of barcode reader.

Stage 6 Gantt chart action based on stage one to five

Figure 4 Details vies of system scope and software requirements

Figure 5 Details view of system deign and testing plan

Figure 6 Details view of training methodology and system documentation

Figure 7 Details view of Pilot, deployment and post implementation review

1 System scope 3,275.35 37.65 0.00 3,313.00 3,313.00

2Software 8,266.04 363.96 0.00 8,630.00 8,630.00

3 Design 10,730.53 652.47 0.00 11,383.00 11,383.00

4 Testing plan 2,910.24 41.76 0.00 2,952.00 2,952.00

5 Training 5,079.34 985.66 0.00 6,065.00 6,065.00

6System 7,689.88 272.12 0.00 7,962.00 7,962.00

7 Pilot 2,843.12 92.88 0.00 2,936.00 2,936.00

SAR system 0.00 0.00 0.00 0.00 0.00

Vous aimerez peut-être aussi