CIS 2303 – Systems Analysis and Design Project Report, AY 2022
Computer and Information Science
Project Report
Course CIS2303- Systems Analysis and Design 2022-20
Assessment Method Group Project – WRITE THE NAME OF YOUR SYSTEM HERE
Date of Assessment Week 5 – Week 15 Deadline(s) Submissions:
th
Draft Submission – 19 April 2023 Week 15
(Introduction, Methodology,
Feasibility, Requirements Gathering,
Perimeter of System-to-be)
Report Submission – 25th April 2023
Presentation – 27th April 2023
Maximum Mark 100 Percentage of Final Grade 25%
The entire project document is designed and developed by me (and my team members).
The proper citation has been used when I (and my team members) used other sources.
No part of this project has been designed, developed or written for me (and my team members) by a third party.
I have a copy of this project in case the submitted copy is lost or damaged.
None of the music/graphics/animation/video/images used in this project have violated the Copy Right/Patent/Intellectual Property
rights of an individual, company or an Institution.
I have the written permission from people who are featuring in this project.
Date: 26 / 01 / 2023
Student HCT ID Student Name Signature
H00443068 Ahmed Hasan AL Shehhi
H00461374 Obaid Arif Obaid Rashed Almheiri
H00414384 Ghaith Bader Zain Ahmad Alsharif
H00443110 Rashed Abdullah Yaqoob Al khadar
PAGE: 1
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
<<Press Function Key F9 to update this table of contents>>
CONTENTS
Table of figures.................................................................................................................................................................................. 3
Introduction....................................................................................................................................................................................... 4
Methodology..................................................................................................................................................................................... 4
Feasibility study of the to-be system.................................................................................................................................................4
Requirements Gathering................................................................................................................................................................... 5
Perimeter of System to-Be.................................................................................................................................................................5
Activity Diagram................................................................................................................................................................................ 6
List of Functional and Non-Functional Requirements........................................................................................................................6
Use Case Diagram.............................................................................................................................................................................. 7
Textual descriptions of two use cases................................................................................................................................................8
System sequence diagram.................................................................................................................................................................9
Domain class diagrams...................................................................................................................................................................... 9
Iteration 1 Inlcude Class diagram with classes and attributes....................................................................................................9
Iteration 2 Inlcude Class diagram with classes, associative classes, attributes with data types and operations........................9
High-level architectural model of the to-be system...........................................................................................................................9
Justification of architectural model...................................................................................................................................................9
Sample user interface and reports.....................................................................................................................................................9
Conclusion and individual reflection..................................................................................................................................................9
Evidence from requirements gathering...........................................................................................................................................10
References....................................................................................................................................................................................... 10
Attachments.................................................................................................................................................................................... 10
PAGE: 2
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
TABLE OF FIGURES
Figure 1.............................................................................................................................................................................................. 6
Figure 2.............................................................................................................................................................................................. 7
Figure 3.............................................................................................................................................................................................. 8
Figure 4.............................................................................................................................................................................................. 8
Figure 5.............................................................................................................................................................................................. 9
Figure 6.............................................................................................................................................................................................. 9
Figure 7.............................................................................................................................................................................................. 9
Figure 8.............................................................................................................................................................................................. 9
Figure 9.............................................................................................................................................................................................. 9
Figure 10............................................................................................................................................................................................ 9
Figure 11............................................................................................................................................................................................ 9
Figure 12.......................................................................................................................................................................................... 10
Figure 13.......................................................................................................................................................................................... 10
PAGE: 3
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
INTRODUCTION
Electric cars are becoming more popular but it can be hard to find a charging station. Different charging stations uses different
payment systems which can make it difficult to use them. To make things easier we need a system that is easy to use and shows
you where to find charging stations and It should also tell you how much time you have left to charge and let you pay for the
charging easily.
METHODOLOGY
A) Structured development is a way of developing software that follows a step-by-step approach. It involves
understanding the requirements of the software, designing it, writing the code, testing it, and maintaining it over time.
Advantages:
1- Uses clear structure
2- Determines the end goal early
Features :
1- There are no ambiguous requirements.
2- Technology is understood and is not dynamic.
Disadvantages:
1- Makes changes difficult
2- Excludes the client
Citation : One of the key strengths of structured development is its emphasis on modular design and structured programming
techniques. By breaking down a software system into smaller, more manageable modules, developers can more easily manage
the complexity of the system and improve the maintainability of the code. Additionally, the use of structured programming
techniques, such as the use of control structures like loops and conditionals, can improve code clarity and reduce the likelihood
of errors. Mauro, R., & Holzner, S. (2014). Structured Development
Iterative development : is a way of building software by breaking it down into small pieces, building and testing each piece, and
then putting them all together. This helps the development team to work quickly and adapt to changes in requirements or
feedback from stakeholders.
Advantages:
1- In iterative model less time is spent on documenting and more time is given for designing.
2- Risks are identified and resolved during iteration
Features :
1- Collaboration between the development team and stakeholders
2- Continuous feedback and testing
Disadvantages:
1- More resources may be required
2- More management attention is required
PAGE: 4
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
Citation : Iterative development is an approach to software development where requirements and solutions evolve through
multiple iterations or cycles of planning, designing, building, testing, and evaluating. The idea is to break down the development
process into smaller, more manageable pieces that can be tested and refined before moving on to the next iteration. This
approach is often used in Agile methodologies such as Scrum and Kanban. Larman, C., & Basili, V. R. (2003).
B) Agile development : is a way of making software that emphasizes teamwork, flexibility, and customer satisfaction. It
involves breaking the project into small pieces and delivering a working product quickly, with frequent communication
and feedback between the development team and stakeholders.
Advantages:
1- Improved quality
2- Speed and flexibility
Features :
1- Customer collaboration
2- Adaptability to change
Disadvantages:
1- difficult to predict efforts at the beginning
2- Customer availability
Citation : Agile development is a software development methodology that emphasizes flexibility and rapid iteration. It is
based on the Agile Manifesto, a set of guiding values and principles for software development that prioritize individuals and
interactions, working software, customer collaboration, and response to change. Beck, K., Beedle, M., van Bennekum, A.,
Cockburn, A., Cunningham, W., Fowler, M., ... & Thomas, D. (2001). Manifesto for Agile Software Development. Agile
Alliance.
We will use the agile methodology as the ev charger station requires continues collaboration between the customer and
stakeholders and its flexible with any changes that happens in the ev charges industry.
FEASIBILITY STUDY OF THE TO-BE SYSTEM
1. Economic Feasibility
1.1. Costs of the System Components
<<Update data in this table with realistic values>>
Total Subtotals Source
Software $2855 $3000 https://aiven.io/kafka-plan-
Database finder?tab=plan-pricing
Hardware $3392 $3500 server
Server
People – Salaries: Developers: $6000 $6500 developers
Developers Testers: $8200 $8300 Testers
Testers Project manager: 19500 $20000 projectManager
Project Manager Analyst : $12000 $13000 analyst
Analyst
Total $45700 $47800
PAGE: 5
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
1.2. Benefits of the systems to be
As been said above the system will show you where to find charging stations and It should also tell you how much time you
have left to charge and let you pay for the charging easily.
2. Legal Feasibility
There are a lot of legal factors that needs to be considered but the most important factors are :
- Data privacy: ensure user data is protected and managed appropriately
- Insurance : helps to protect against financial risks associated with accidents, property damage, or other liabilities that
may arise from the operation of the charging station
- Permit: for installation ensure that the charging station is installed in a safe and compliant manner
3. Technical
There are a lot of technical factors that needs to be considered but the most important factors are :
- Availability : as we have to make sure that the system can be accessed by all users including those with disabilities
- Charging protocols: the system must support appropriate protocol for the EV
- Payment system : the payment system should be secured and reliable
4. Operational
There are a lot of operation factors that needs to be considered but the most important factors are :
- Charging time : The charging station should provide a fast and seamless charging experience
- Customer Service and Support : A reliable and responsive customer service and support system
- Network and Data Management : The charging station should be connected to a network to enable energy
consumption, and payment processing.
5. Schedule
There are a lot of schedule factors that needs to be considered but the most important factors are :
- Charging Station Capacity: The charging station capacity should be appropriate for the expected charging demand
- Grid Capacity: The charging station system should consider the grid capacity and ensure that the charging demand does
not exceed the local power supply.
Feasibility Evaluation:
After going throughout all of the factors we can see that our system is compatible with all of the factors, but there are several
challenges that needs to be addressed such as charging time, payment processing, and schedule feasibility.
PAGE: 6
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
REQUIREMENTS GATHERING
There are several techniques that can be used for gathering requirements and its important to understand the requirements
through the techniques such as Interview, Survey of Users, and document analysis as it will give the developers an insight of the
users needs and use this information to develop a system that meets their requirement. In order to get the requirements We
have made an interview with chatGPT and asked the following:
A)What features do you find most important in an EV charging station?
B)What payment methods do you prefer for charging EV?
C)What are the difficulties while using EV charging stations according to recent surveys?
D)How do you want to process your payment after charging?
E)what are the most common difficulties that user face will using a certain system?
F)what would you like to have in the receipt after the payment is done?
And its response was :
A - based on user surveys and research, here are some features that are generally considered important in an EV
charging station:
- Compatibility with different types of electric vehicles and charging protocols
- Fast and efficient charging times
- Availability and accessibility of charging stations
- User-friendly interfaces and payment systems
- Real-time monitoring and display of charging progress and battery status
- Safety features such as automatic shut-off and protection against overcharging
- Reliability and maintenance of the charging station equipment
- Energy management features such as load balancing and smart grid integration
- Integration with mobile apps and other smart devices ,Environmental sustainability features such as solar panels or
other renewable energy sources.
(OpenAI, 2023)
B - Credit or debit cards , Mobile apps, Membership programs, Contactless payment, Prepaid cards or vouchers
(OpenAI, 2023)
C - Lack of availability, Payment difficulties, Technical malfunctions, Slow charging speeds, Compatibility issues
(OpenAI, 2023).
D - As an AI language model, I don't have a personal preference for payment processing. However, for an EV charging
system, there are various payment processing options that could be implemented, such as credit/debit card payments,
mobile payments, or even subscription-based payment models. The choice of payment processing method would
depend on factors such as the target audience, security considerations, and the level of convenience offered to the
user. Once the payment is completed, it would be ideal to provide the user with a notification to confirm that the
transaction has been successful.
(OpenAI, 2023).
PAGE: 7
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
E- As an AI language model, I can provide some common difficulties that users may face while using a system:
Complexity: Users may find the system too complex to understand or use.
Navigation: Users may have trouble finding their way around the system, especially if the system has a lot of features
and functions.
Error handling: Users may encounter errors while using the system, such as technical errors or input errors, and may
not know how to fix them.
Performance: Users may experience slow system performance, especially if the system has a lot of data or complex
processing requirements.
Compatibility: Users may encounter compatibility issues with the system, such as compatibility with different devices or
software versions.
By addressing these common difficulties, a system can be designed to be more user-friendly and efficient.
(OpenAI, 2023).
F- As an AI language model, I don't have a personal preference for the contents of a receipt. However, some common
items that users might like to see on a receipt after payment for an EV charging station could include the date and time
of the charging session, the duration of the session, the amount of energy consumed, the total cost of the session, and
any taxes or fees associated with the charging service. Other items that could be included on a receipt might depend on
the specific payment processing method used and any additional services or features offered by the charging station.
(OpenAI, 2023).
PERIMETER OF SYSTEM TO-BE
<<Summarize perimeter/boundary of the system. Write this in the format of a list. These are the main use cases of your
system>>
The EV Charging system performs the following functions:
1. Charge EV battery
2. monitors the charging process
3. provides information about the charging status to the user
4. process payment
The EV Charging system does not include the following:
1- communication system
2- shopping system
PAGE: 8
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
ACTIVITY DIAGRAM
<< Create in StarUML and Insert screenshot of the Activity Diagram. Use swim lanes, nodes, branches/forks as necessary >>
Figure 1
PAGE: 9
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
LIST OF FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
<< Create a list of Functional and Non-Functional Requirements based on the FURPS models. In case of Functional requirements,
consider inputs, processes/calculations, and outputs. Write these in the format of user stories. These should be based on your
research, interview, and details in the case study)
- As an AI I would like to have a Real-time monitoring and display of charging progress and battery status so the user can
manage their charging .
- As an AI I would like to have a secure transaction so the user can pay safely
- As an AI I would like to have an easy system so the user can use the system without any difficulties
- As an AI I would like to have a fast system so the user can get an instant reply from the system
- As an AI I would like to have no errors in the system so the user may no know how to fix these errors
- As an AI I would like to have receive a notification so the user can know that the transaction was completed successfully
- As an AI I would like to receive a total cost in the receipt so the user can know the total cost of the charging session.
- As an AI I would like to select an available charger so the user can charge his EV.
Functional Requirements
Category Requirements written as a User Story Priority(H/M/L)
Inputs Select available charger M
Process Monitor charging L
Calculations Calculate Total charging cost H
Outputs Send notification L
Non-Functional Requirements
<<Write the following non-functional requirements in the form of user stories>>
Category Requirements written as a User Story Priority(H/M/L)
Usability The system will be easy to use M
Reliability The system will have no errors H
Performance The system will respond to users instantly M
Security The system will secure data throughout encryption H
PAGE: 10
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
USE CASE DIAGRAM
Actors :
1. EV Owner: The person who owns the electric vehicle and wants to charge it.
2. Charger Station: The physical charging station that provides charging services for electric vehicles.
3. Payment Gateway: The payment processing system that handles payment transactions.
4. Employee: The employee who manages the operation and maintenance of the charger station.
PAGE: 11
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
TEXTUAL DESCRIPTIONS OF TWO USE CASES
<<Write the textual description for two of the most complex use cases, documenting in the template given below>>
Use case name: verify availability ID: 1
Primary Actor: charging station
Secondary Actor: EV Owner
Brief Description: the charging station will verify if the selected charger is available
Normal flow of events:
EV owner System Charging station
Log in account Log in successfully
Select charger spot Forward for verification Checks if the selected charger
is available
Confirm validation
Send confirmation message
Forward confirmation
Plug charger
Alternative Flows:
- If the selected charger is not available the charging station will display unavailability
- If the Charger Station system encounters an error while checking the availability of the
charger, the system displays an error message to the EV Owner and prompts them to try
again later.
Figure 2
Use case name: verify paymentDetails ID: 2
Primary Actor: payment Gateway
Secondary Actor: charging station
Brief Description: the payment gateway will verify the payment details and check if the transaction
is done successfully
Normal flow of events:
Charger station system EV owner Payment
gateway
Send payment details Forward payment Check of the
details details validation
Confirm
validation
Send validation
Forward validation
Send notification Forward notification Receive notification
Alternative Flows:
If the payment details were invalid the gateway will send an error message to the charging
station.
Figure 3
PAGE: 12
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
SYSTEM SEQUENCE DIAGRAM
Use case 1 : check availability
Figure 4
PAGE: 13
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
Use case 2 : verify payment details
PAGE: 14
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
DOMAIN CLASS DIAGRAMS
ITERATION 1 INLCUDE CLASS DIAGRAM WITH CLASSES AND ATTRIBUTES
Figure 5
ITERATION 2 INLCUDE CLASS DIAGRAM WITH CLASSES, ASSOCIATIVE CLASSES, ATTRIBUTES WITH
DATA TYPES AND OPERATIONS
PAGE: 15
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
Figure 6
HIGH-LEVEL ARCHITECTURAL MODEL OF THE TO-BE SYSTEM
Figure 7
JUSTIFICATION OF ARCHITECTURAL MODEL
There are many strengths that the three layer architecture model has such as :
PAGE: 16
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
- Scalability: The three-layer architecture is highly scalable because each layer can be scaled independently of the others
- Reusability: The three-layer architecture promotes code reuse because each layer can be used in multiple applications or
components
- Testability: Because each layer of the three-layer architecture can be tested separately which will lead to reducing bugs
Citation :
- One study by Haider et al. (2020) evaluated the effectiveness of three-layer architecture in improving software quality
attributes such as maintainability, modularity, and scalability. The study found that the three-layer architecture helped
to improve these attributes and contributed to better software quality overall. Haider, S., Khattak, M. A. K., & Saeed, U.
(2020).
- Another study by Guo and Wen (2014) evaluated the three-layer architecture in terms of its modularity and
extensibility. They found that the three-layer architecture provided good support for modularity and extensibility,
which made it easier to add new features to an application. Guo, H., & Wen, L. (2014).
SAMPLE USER INTERFACE AND REPORTS
<<Sample of THREE SCREENS developed using the best practices of user interface discussed in Chapter 7>>
Prototype : https://www.figma.com/proto/o1UhFAep1FrGUB4CJebfZr/Ev-charging-station-system?node-id=1-3&scaling=scale-
down&page-id=0%3A1&starting-point-node-id=1%3A3
Sketch:
PAGE: 17
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
Storyboard :
CONCLUSION AND INDIVIDUAL REFLECTION
PAGE: 18
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
In this project we have achieved a lot although it was done in a small period but the outcome was phenomenal, what we
achieved was great because we faced many challenges like making a prototype, trying to connect diagrams depending on
assumptions etc.. but because we worked as a team we had the chance to hear brilliant ideas from each other and try to
implement our skills into the project and that lead us into getting an interesting project.
Ahmed Hasan : I have learned a lot in this project specially from my teammates as each one of them has different skills that I
really benefited from, not only that my teamwork skills and confidence has grown rapidly during this project. I have shared my
ideas and skills with my colleagues in that way I was able to contribute the team in this project. We were able to share our work
evenly and after each completed part we meet and give our feedback .
Ghaith AlSharif : I have learned form this project how does system analysis really have deep level of steps and how that
different diagrams play different roles and perspective to the project which allows me to have a better understanding of the
project, which will lead to better result toward the end
Obaid Almheiri: I have learned from this project the impact of system analysis in projects and how it could help in projects by
analyzing the situation in different ways and creating many steps to help you understand stand the project or a business which
will help you get better results
Rashed Al khadar : I have learned form this project how to understand the infrastructure of a system, and how does this course
system analysis have extended in deep detail of steps and how that different diagrams play a specific roles and prespective to
this project which allows me to have a better understanding of this project, which will lead to better result toward the end of
this course and extends to my future.
EVIDENCE FROM REQUIREMENTS GATHERING
B
PAGE: 19
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
PAGE: 20
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
PAGE: 21
CIS 2303 – Systems Analysis and Design Project Report, AY 2022
REFERENCES
- Dijkstra, E. W. (1972). The humble programmer. Communications of the ACM, 15(10), 859-866. Mauro, R., & Holzner, S.
(2014). Structured Development. In Objective-C for Absolute Beginners: iPhone, iPad, and Mac Programming Made Easy
(3rd ed., pp. 135-145). Apress.
- Larman, C., & Basili, V. R. (2003). Iterative and Incremental Development: A Brief History. IEEE Computer, 36(6), 47-56.
https://doi.org/10.1109/MC.2003.1204375
- Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., ... & Thomas, D. (2001). Manifesto
for Agile Software Development. Agile Alliance. https://agilemanifesto.org/
- OpenAI. (2023). ChatGPT (Mar 14 version) [Large language model]. https://chat.openai.com/chat
- Haider, S., Khattak, M. A. K., & Saeed, U. (2020). Three-Layer Architecture: A Comparative Study for Software
Development. Journal of Software Engineering and Applications, 13(1), 1-15.
- https://doi.org/10.4236/jsea.2020.131001
- Guo, H., & Wen, L. (2014). An Empirical Study on the Modularity and Extensibility of Three-Tier Architecture. Journal of
Software Engineering and Applications, 7(10), 855-863. https://doi.org/10.4236/jsea.2014.710077
ATTACHMENTS
File names of all models created in StarUML
File names for Models: GROUPNUMBER-MODELNAME.
End of Report 😊
PAGE: 22
