Professional Documents
Culture Documents
Requirements Document For An Information System Development Project
Requirements Document For An Information System Development Project
FOR AN INFORMATION
SYSTEM DEVELOPMENT
PROJECT
CMPG213 PROJECT PHASE 2
•1. Project Plan
•2. Definitions, acronyms and abbreviations
•3. Project description and Scope
•4. Functional requirements i.e.
• a) business data requirements (inputs, outputs)
• b) business processes requirements
CONTENT
•5. Non-functional requirements (categorized according to the PIECES
Framework)
•6. Candidate Systems Matrix
•7. Feasibility Analysis Matrix
•8. Use-Case Glossary & Use-Case Model Diagram
•9. Examples of data, questionnaires, fact-finding techniques used
•10. Summary, future and further planning(PERT Chart)
1. PROJECT PLAN
1. PROJECT PLAN
1. PROJECT PLAN
2. DEFINITIONS, ACRONYMS AND
ABBREVIATIONS
Abbreviations
• PERT Chart: Program Evaluation Review Technique Chart
• GUI: Graphical User Interface
• COTS: Commercial Off-The-Shelf
Definitions
GANTT Chart: A bar chart that is used to illustrate a project schedule. The tasks are placed on
the vertical axis with the time needed for each phase being put on the horizontal axis.
PERT Chart: A tool used to plan, organize, schedule and coordinate tasks within a project.
USE-CASE: A diagram that depicts the interactions between the system and external systems
and users.
3. PROJECT DESCRIPTION AND SCOPE
Animal Control
maintain animals
Login form
Booking
manage bookings
administrators
maintain animals
reports
Maintenance of Animals
Deleting of guests
Change Booking
Deleting of bookings
Help functions will be include with tool tips Efficiency of people and processes
Candidate is not currently The server will be able to A custom system will be
The portion of computerized. Data is use Linux. PostgreSQL is created to keep track of the
the reserve that stored physically. expected to help the booking of visitors and the
applicant's information addition as well as loss of
will be base. animals, it will also be able
computerized to separate the endangered
animals list for the other
6. CANDIDATE
animals and.
SYSTEMS MATRIX
SYSTEMS MATRIX
A keyboard and
mouse are also
needed for
information
input into the
GUI.
Candidate 1 Candidate 2 Candidate 3
AS – IS COTS Package Custom Designed
Software Solution Solution
(Oracle)
Characteristics
Technical 20 This candidate is usable, but This candidate could be easy to This candidate will be programmed
feasibility to make change when navigate when creating the system, in a Visual basic - C# and will make
developing the system could but since the project team have no use of Sql database software. The
prove to be very hard. prior experience with this project team is very familiar with
programming language, it would this computer language and
take them excess time to even database software. The project
learn the basic fundamentals that team would have no issues
this language and software designing the system with these
requires. Also considering that the restrictions.
team has to learn so much
information that might lose sight of
the true system forget to implement
various key parts.
Score: 10 Score: 50 Score: 90
7. FEASIBILITY ANALYSIS MATRIX
Operational 15 This candidate system is This candidate has great potential This candidate will fulfil all of the system
currently implemented at the to fulfil most of the requirements, users’ requirements. It will provide
feasibility special features such as the organizing
national park, it does not only but it still has issues regarding the
of regular animals and endangered
lack the desired requirements making of reports. This candidate species. The candidate will, like
needed for this system but could potentially increase work candidate 2, increase productivity. The
also resolves in data loss. It is productivity as well as help the workers can now spend more time
unable to automate entering workers to store more information tending to the visitors instead of
data directly into the system safely. Unfortunately the system painstakingly adding data manually to a
and has problems keeping does have a learning curve so the database. Interfaces for this system will
track of visitor bookings. Due average user will struggle. The be user-friendly and thus easily
to the manual implementation system is also not very popular and navigable. A help line will also be
provided for those that still struggle to
of data, this system wastes might have some defects. use the system. The new system will
too much time. take some adjustment from the system
users.
Score: 30 Score: 50 Score: 90
7. FEASIBILITY ANALYSIS MATRIX
Risk 15 This system does not make The project team would struggle to The project team have years of
feasibility use of digital data like the create this system, because they training with this computer
other systems. Due to the fact would lack the knowledge to utilize language and database software
that most of the data is the technologies/software that are used to make this system. There is
physical, it could lead to loss required in this candidate. Thus a low failure rate to create this
of data. there is a high failure rate. system.
Economic 10
feasibility
The cost to
N/A Approximately R 407 124 Approximately R 980 010
develop:
Net present
N/A R 149 668 R256 770
value:
Schedule 10 If this candidate is chosen, no The project team have had no This candidate has a high chance
feasibility changes will have to be additional training with this of completing the system in time,
made. programming language, so the because the project team have a lot
chances of having a delay in the of experience with this
schedule would be very high. The programming language and
team would need excess time to software. Unfortunately they would
complete the system in said have to rebuild the system using
programming language. (5 extra this code. (8 months)
months)
Cultural 15 The users show a lot of Less resistance could be shown by Some resistance may be
feasibility resistance to this solution. the users, but this system may still experienced by users. The
be challenging for some users and resistance that users may feel for
have a learning curve. this candidate can be lowered by
personalising the system for their
users.
Use Case Name Use Case Description Participating Actors and Roles
Log into system Users log into the system using a Administrator(s)
Username and Password. Users
Maintain animals The event where new and existing animals Administrator(s)
will be monitored(e.g. number of animals, Rangers
endangered species and where they go).
Maintain bookings The event where all bookings made are Administrator(s)
kept record off. They can be changed,
deleted and new ones can be added.
Maintain Payments All payments for bookings are kept record Administrator(s)
off.
Arrival of Guests Dates that guests can arrive if they have Administrator(s)
booked and the booking was successful. Users
Departure of Guests The date that guests must departure. Administrator(s)
Users
9,18 27,36
C
A 18
0,0
9