0% found this document useful (0 votes)
20 views51 pages

UIU Online Exam System Design Overview

The document outlines the concepts and methodologies of System Design within the context of System Analysis and Design, focusing on the Software Development Life Cycle (SDLC). It covers various design specifications, including system requirements, process flow diagrams, business rules, database design, and user interface design, along with different types of diagrams such as UML, context diagrams, and data flow diagrams. Additionally, it provides examples of use case diagrams and activity diagrams, illustrating the relationships and processes involved in system design.

Uploaded by

2310884
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views51 pages

UIU Online Exam System Design Overview

The document outlines the concepts and methodologies of System Design within the context of System Analysis and Design, focusing on the Software Development Life Cycle (SDLC). It covers various design specifications, including system requirements, process flow diagrams, business rules, database design, and user interface design, along with different types of diagrams such as UML, context diagrams, and data flow diagrams. Additionally, it provides examples of use case diagrams and activity diagrams, illustrating the relationships and processes involved in system design.

Uploaded by

2310884
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Slide # 3

CSI 311, System Analysis and Design

System Design
2
SDLC
Syste
Concept m
Desig
n
3 System Design Specifies:

✔ System Requirements
✔ Process Flow/ Diagram
Syste
✔ Business rules etc.
m ✔ Database Design
Desig ✔ System Visualization/ UI Design
n ✔ System Architecture (2 Tier, 3 Tier, Cloud, MVC )
Different Diagrams:

4 OO Design
(UML Diagrams)
▸Context Diagram.
Structured Design
▸Data Flow Diagram.
▸E-R Diagram
UML ▸Use Case Diagram *
▸Decision Tree
▸Activity Diagram.
Desig ▸Swim lane Diagram ▸Decision Tables
n ▸Class Diagram ▸Structured English
▸CRC
▸Sequence Diagram
▸State Diagram.
▸Deployment Diagram
▸ UI Design/Visualization
UML Highlights:

5 UML
• The current version of UML, Version 2.0,
• It was accepted by the Object Management
Group (OMG) in 2003.
Diagram
• This version of UML defines a set of 14
s
diagrams for modeling a system.
• The diagrams are broken into two
groupings: Structural diagrams, Behavioral
diagrams
Context Diagram

6 • Bird’s Eye View of a System


• It contains only one process (Process
0), that represents the Whole System

• System or the Process Zero node is


connected with the External Entities
(EE)/ Stake Holders or the type’s of
user of the System
Rules to Draw:

7
Context
• Only one process (numbered 0)
• External entities as Squares, Rectangle
• Line shows data flows
• External Entities are written in Capital letter
Diagram
• Process Name written in First Letter in Capital form
Context Diagram

8 ADMIN

0
UIU
STUDENT RESEARCHERS
Management
System

TEACHERS
Context Diagram

9
1 Benefits of using a context
diagram

0
▸Easy to Understand
▸Reduce Risks
▸Enables Collaboration
Use Case
• Use cases are the primary drivers for all of the UML
diagramming techniques.
• Use case diagram emphasis on what a system does
rather than how.
• Use case diagrams are closely connected to scenarios. A
scenario is an example of what happens when someone
interacts with the system.
Use Case
• A use case is a
summary of scenarios for
a single task or goal.

• An actor is who or what


initiates the events or
task. Patient
Make
Appointment

• The picture below is a


Make Appointment use
case for the medical
clinic. The actor is a
Patient.
Four Major Symbols of Use Case Diagram
Relationship among Uses Cases

• Include (mandatory execution relationship)


• Extend (optional execution relationship)
Symbols of Use Case Diagram
Example: Use case Diagram
To describe an Use Case

1. Use case number and name


2. Primary Actor
3. Stakeholders and Interests
4. Preconditions
5. Success Scenario
6. Alternate Scenario
7. Post-conditions
Example: Use case of a Sells System

Customer
Cashier Sell Item
UC 01: Sell Item
▸Primary Actor: Cashier

Stakeholders and Interests:


▸Cashier: Wants accurate, fast entry and no payment errors
▸Customer: Wants purchase and fast service with minimal effort.
Wants receipt if future return of product is necessary.
▸Company (owner): Wants to accurately record
transactions and satisfy customer interests.
▸Government Tax Agencies: Wants to collect tax from
every sale.
Preconditions

▸Preconditions: Cashier is identified and


authenticated.
Success Scenario
▸[Link] arrives at counter with goods to purchase.
▸[Link] starts a new sale.
▸[Link] enters item identifier.
▸[Link] records sale item and presents item description,
price and running total
Cashier repeats steps 3-4 until indicates done
Success Scenario ( Cont..)
▸[Link] presents total with tax calculated.
▸[Link] tells customer the total and asks for payment.
▸[Link] pays and system handles payment.
▸8. System presents receipt.
▸[Link] leaves with receipt and goods.
Alternative Scenario:

*a At any time, System can fail:


▹1. Cashier restarts System, logs in and request recovery of prior state.
▹2. System re-constructs prior state.
3. Invalid identifier (scanner does not work):
▹1. Signals system error and rejects entry.
▹2. Manual Entry given
Alternative Scenario (cont..)
3-6 a) Customer asks cashier to remove an item.
i. Cashier enters item identifier for removal of sale.
ii. System displays updated running total.

3-6 b) Customer tells cashier to cancel sale


i. Cashier cancels sale on System.
Post-conditions: Sale is saved. Tax is correctly calculated.
Accounting and inventory updated. Receipt is generated.
Activity Diagrams

2 • Similar to Flow Chart

8
• Start and end points are different

• Control flow should be signed by the arrow

• Common components of activity diagrams are:


Action, Start State, End State, Fork and Join,
Decision.
2
Activity Diagram
Before drawing an activity diagram, we
should identify the following elements −

9 •Activities
•Association
•Conditions
•Constraints
Symbols of Activity Diagram
Activity Diagram of User/Visitor

3
1
Activity Diagram: Cash Withdraw/ Deposit
Activity Diagram: Withdraw money at ATM Booth
Leave Management: Activity Diagram
Leave Management: Activity Diagram
Swim lane Diagram

• A Swimlane Diagram is used in process flow diagrams, or


flowcharts, that visually Distinguishes Job sharing or
Responsibilities among different Stakeholders for
different activities or processes.

• Swimlane may be arranged either horizontally or vertically.


Swim lane Diagram
Swim lane Diagram
Swim lane Diagram
DFD: Data Flow Diagram

• Data Flow Diagram is a way of representing a flow of


data through a process or a system.
• DFD provides information about the outputs and
inputs of each entity and the process itself.
• DFD has no control flow, there are no Decision rules
and no Loops
DFD Symbols
Rules of DFD
•Four Symbols: Process, External Entity (EE),
Database(DB)/Table, Data Flow
•Database/DataStore, External Entities: ALL Capital
letters
•Process naming: First letter of each Word in Capital
letter
•DFD starts from Top-Left and ended at Bottom-Right
•No connection: DB to DB, DB to EE, EE to EE
•Each Process and Sub Process must have Name and
Number
Data Flow Diagram (Level 0)
DFD: Food Ordering System
• A Food Order system is described below:

• A Customer can place an order in the Food Order System. As soon as the order is
received it is processed and forwarded to the Kitchen. The order is stored in the
Order data store and the updated Inventory details is stored in the Inventory data
store. The process also delivers a Bill to the Customer.

• A Manager can receive Reports through the Generate Reports process, which
takes Inventory details and Orders as input from the Inventory and Order data
store respectively. He/She can also initiate the Order Inventory process by
providing Inventory order. The process forwards the Inventory order to the
Supplier and stores the updated Inventory details in the Inventory data store.

• Draw a Data Flow Diagram of the Food Order System


DFD: Food Ordering System
DFD: eLearning System
DFD Elements

Proce
ss
Data
flow
Data
store
Exter
nal 6 - 48
entity
Relationship Among DFD levels
Context
diagram

Level 0
DFD

Level 1
diagram

Level 2
diagram
Suppose you are asked to do the design for a software module within UCAM named - UIU Online Exam
System (UOES). In a trimester, the registered students and respective teachers’ will automatically
receive the invitation (including userID and password) through email from UOES for a particular section
of respective course. After accepting the invitation both teachers/students will be allowed to
create/participate into the online exams. UOES has the option to create the online exams by the
teachers using MCQ questions and respective answers entry. In addition to text entry, teachers can
enter different pictures/audio files as a part of questions. Teachers can create a customized schedule for
different exams and can take attendance and calculate marks of the examinees automatically. Students
can participate the exams and receive the results immediately after their exams. At the end of each
exam, UOES automatically save the exams related data/info into UIU’s cloud server. UOES Admin
resets/refreshes all the exam info for serving for the coming trimester – this process is termed as
Refresh. Consider necessary required files as per your convenience.

Draw USE CASE diagram for the above scenario (show at least one include and extend connections).
i. Mention the reasons for selecting those as Use Cases.
ii. Write down the rules of DFD. Draw the DFD for the above scenario.
Consider the following scenario of UIU Library Books Rental Service Web application:

“UIU has opened an online book rental system for the students of UIU. A student can rent maximum five books
for 2 weeks. Initially, the student needs to go to the website. The student requests for books through the Rent
Book process from the web application. Students need to provide ID and name for this purpose. The process
uses the STUDENT database to verify the ID and name. If the information does not match, The Error process
will be initiated to show invalid message and ask for re-entering the information. If the information is valid, the
BOOK database is searched. If the book is unavailable an error message is shown. If the book is found, a
student can select his desired number of book/s in an iterative way. At the end of Rent Book process, the
BOOK_RENT database is updated having the book list, student’s info, and rental duration information. With
these info an invoice is also sent to the student for future reference. The student needs to go physically to the
university library for receiving the books.

At the time of returning the books, a student needs to return those to an attendant of Library. The attendant
verifies the invoice and uses the Return Book process online to make updates in the BOOK database. If any
student returns the books after due date, a process Calculate Fine initiates, that automatically calculates a fine
and the STUDENT_ACCOUNTS file will be updated having rental info with fine amount. The student has to pay
the fine in the usual way i.e. by going to the bank to deposit cash or through DBBL ATM card. The Accountant
updates the payment updates in STUDENT_ACCOUNTS file”

You might also like