Information Technology Department
Course Title: Information Technology Systems
Course Code: IT281
A. Project Description:
One of the objectives of this course (IT 281) is to acquire the practical skills needed in order to develop an
information system. To meet this objective, a group should be formed to carry out a project. Depending on the
class/section size, the size of the groups should be determined (e.g., 3 or 4 members for each group).
This project should provide you, as a student, the opportunity to plan, analyses, and design an information system,
which is intended to address a real-world problem. To do that, you may need to find an organization that is willing
to grant your team an access to its data or to apply the relevant suitable fact finding techniques, in order to gather the
requirements and to inform the analysis and the design for the new information system. The proposed information
system should be particularly designed to address a current problem in the organization or to enhance the current
Depending on the problem you are tackling by your proposed system, you may choose to design/develop a Website,
Software component, or an application, etc. The activities to be carried out during this project should utilize
materials learned throughout the course (activities, steps, modelling techniques, etc.), so it is recommended that you
get an early start on forming your group and meeting weekly for this purpose.
The system chosen should not be too big or too small; the emphasis on marking will be on the accuracy of the fact
finding and the thoroughness of the final product, NOT its size.
The main deliverable for the project will be in the form of a “systems proposal”. That is, the nature of the
deliverable should be adjusted accordingly, and as relevant to the project. Follow the Project Template for this
purpose. Some model-examples for suitable projects are:
• A point-of-sales (POS) system
• Inventory System
• Payroll System
• Customer Relations Management System
• Job Tracking System.
B. Project Guidelines and Constraints:
You are expected to be strictly following the project guidelines which are as follow:
• Project scope and ideas
o In the appendix for this document, a list of the previous IT281 project are provided. Use this list as
a reference example. You MUST NOT re-choose any of the project that has been chosen in the
previous 3 terms from the current term.
o The chosen system should have, at least, 5 main identifiable functionalities.
• Project activities and tasks
o Work as a team in this project.
o If the workload were not partitioned fairly between the project team members, this should be
obvious in the project-discussion, the underperformed member will be identifiable by the Lab
instructor and hence his/her grade will be highly affected.
o There will be no extension in the submission deadlines. Milestone and deadlines clarified on Table
• Work quality and originality
o The project tasks undertaken in this project should be genuinely YOURS as a group.
o If any information or statements has been quoted or paraphrased from a scientific source, then the
source should be properly cited and the whole reference list should be supplied at the end of the
document. If so, use Harvard style (Author-date system).
o Any project detected with any source of plagiarism (Cheated content, adopting other people’s
work, Non-original work) will be marked ZERO/20.
o Be aware that LMS Blackboard uses plagiarism check tool!
o No handwriting is accepted.
o Use the project template and adhere to its outlines and format ONLY.
o Make sure that the language used in your descriptive paragraphs and statements are
understandable, grammatically adequate and free from typo errors.
o Font to be used is Times New Roman, Size 12 point, applying 1.15-line spacing.
o Only black color font should be used.
o Don’t forget to fill in your project title in the submitted copy, your section along with your team
members’ full names and students’ IDs
o You can use ONLY (StarUml) tool to draw the required UML diagrams.
o Beside the details given in the following table (Table 1), the content of UMLs required
diagrams/models (depth and breadth) are as follows:
▪ 1 Use-Case diagram for the main system (with at least 5 major use-cases) (avoid log
in/log-out and contact-us use cases).
▪ Use-Case FULL descriptions (at least 3 major use-cases).
▪ Activity diagram for each use case, using SWIMLANES technique.
▪ 1 detailed Class diagram (Attributes and Methods)
▪ 1 Architectural Configuration diagram
o Each UML model should be captioned with its relevant name, positioned in the right place under
the relevant section.
o UML diagrams added to the document should be ONLY in Black and White, with a White clear
background (no water signature should be visible).
o Follow the deadlines (STRICTLY) as detailed in Table 1.
o For each group, ONE document should be submitted for each milestone. Use group submission
feature in the Black board. Two IDENTICAL hard and softcopy should be submitted as detailed
in Table 1.
o Softcopy which will be submitted on the blackboard show be submitted as .pdf file.
o Late submission will deduct your corresponding total mark by 1 mark for each day. No
submission will be accepted after 3 days-behind the deadline.
o The final draft of the project, the hard copy which will be handed in, should be soft-binded, using
the first page of the template as the title page.
o All the team members must attend the presentation session and should present and demonstrate
their contribution in the project. You may be discussed, and/or asked to answer questions or
demonstrate your final prototype/product.
o The whole 4 marks will be deducted from the total project mark for a student if he/she student was
absent in the presentation day.
o Failing to comply with any of the previous instructions or adherence to any of the
constraints will affect your project’s total mark.
o Submitting the project report in different format than .pdf will deduct your mark by -1
A. Project Tasks, Deliverable, and Submission Milestones
Table 1: Project Tasks, Deliverables and Milestones Core processes Activities Project Tasks Deliverable Submission Milestones
Core process 1: Identify the problem and document the objective of the system
• Identify the problem and document the objective of the system
• Obtain approval to commence the project
1. A brief introduction to the problem description.
2. Identify all the system capabilities.
3. Describe the business benefits.
System Vision Document
System Vision Document
soft copy via blackboard (Group submission)
24 SEP 2020
by 11:59 PM.
Core process 2:
Plan the project
• Determine the major components (functional areas) that are needed
• Define the iterations and assign each function to an iteration
• Plan one iteration as it is small and straight forward
• Determine team members and responsibilities
1. Determine the major components.
2. Define the iterations and their functions.
3. Determine team members and responsibilities.
First draft of project report
soft copy via blackboard (Group submission
29 OCT 2020
by 11:59 PM.
Core process 3: Discover and Understand Details
• Do preliminary fact-finding to understand requirements
• Develop a preliminary list of use cases and a use case diagram
• Develop a preliminary list of classes and a class diagram
1. Describe (list) the functional requirements
2. Describe (list) the non-Functional requirements
3. List the use cases (names only) and provide the use case diagram
[Refer to slide 30 & 31 of chapter 1 as an example]
4. List the classes (names ONLY not the diagram)
[Refer to slide 32 of chapter 1 for an example]
Preliminarily System Analysis
Core processes Activities Project Tasks Deliverable Submission Milestones
Core process 3 (Cont.):
Discover and Understand Details
• Do in-depth fact-finding to understand requirements
• Understand and document the detailed workflow of each use case
1. Provide the main detailed use-cases descriptions (minimum 3)
2. Provide the main use-case workflow/activity diagrams
Detailed System Analysis
Final project report
Core Process 4: Design System Components
• Define the user experience with screens and report sketches
• Design the database (schema)
• Browser, Windows, or Smart phone
• Architectural configuration (components)
• Design class diagram
• Subsystem architectural design
1. Provide the screen and reports for one of the major use cases.
2. Provide the detailed Class diagram (attributes and methods)
3. Provide the Architectural Configuration diagram
Core Process 5: Build, Test, and
Integrate System Components
• Continue programming (build)
• Build use case by use case
Linking the screens provided in Task 5, together,
to be able to show the corresponding system functionality in real-time
System Implementation & Testing
Core Process 6: Complete System Testing and Deploy the System
• Perform system functional testing
• Perform user acceptance testing
• Possibly deploy part of system
Presentation and discussion of the project and the system
(Coding is not required)
Discussion and demonstration
B. Marking Scheme
Table 2: Project Marking Scheme
Qualify of Total Marks as
System Vision Document
Lab instructor’s approval to proceed
Project report Version1
Project report Version2
Navigational linked Screens for the main functionality of the system + PPT (non-mandatory)
(Demonstration using appropriate tool)
(Discussion, handling questions)
3 Total 20
Appendix A: Previous Projects’ Topics
My Mall Mobile application
IMAMU Student Parking Lot
Finding Auto Parts
Finding lecture room in IMAMU
Food Storage System
Ikea (E-commerce and Shipping)
MY_STC (Account Management)
Booking appointments (Mawid) for governmental organizations
Wassel (Food Delivery)
AlDanoub (Grocery and Shipping) Spring 2020
Appendix B: Example of System Vision Document (To be approved by Lab-Instructor)
Such a cheap price for your free time and healthy sleep
All online transactions are done using all major Credit Cards or Electronic Check through PayPal. These are safe, secure, and efficient online payment methods.