Author
Table of contents
1. Context for system analysis
1.1. Description of the organization (detailed description of the department/area
of planned system application)
1.2. Organizational structure diagram
1.3. Users’ requirements identification and description
2. Functional scope – functional structure of the system
3. List and description of system users – user/function table
4. Use case models – diagrams with specification
5. Information structures modeling – class diagram
6. Interaction models - sequence and communication diagrams (for at least 4 use
cases)
7. System operation modeling – activity diagrams (for at least 4 use cases)
8. Modeling object classes behavior – statechart diagrams for object classes (at least
3 diagrams)
9. System architecture modeling – package diagrams
1. Context for system analysis
1.1. Description of the organization (detailed description of the
department/area of planned system application)
Description of the organization – what is the profile of the organization, what kind of services
does it provide, what departments/sections does it have and what is done by people in those
departments/sections, how does the interaction with the client look like.
A few more words describing the department (-s) where the information system is planned to be
implemented and what activities (operations) it is supposed to support.
1.2. Organizational structure diagram
Organization
Department 1
Department 2
Department 3
Description of each department – what is being done there
1.3. Users’ requirements identification and description
Description of general requirements for the system – main tasks of the system (what will the
system generally support)
Description of functional requirements – system functions, data (input and output data), system
users (who will use it and for what purpose)
Description of non-functional requirements – quality requirements (safety, reliability etc.),
interface requirements
Description of environment requirements – architectural (hardware, software), performance and
documentation, standards and interfaces to other systems (if applicable)
Description of design and implementation requirements – cost and time limits, development
environment (if applicable), methods of validation and testing
2. Functional scope – functional structure of the system
1. Function 1
2. Function 2
3. Function 3
3.1. Subfunction of Function 3
3.2. Subfunction of Function 3
4. Function 4
5. …..
3. List and description of system users – user/function table
System users (roles)
System functions
Function 1
Function 2
Function 3
Subfunction of Function 3
Subfunction of Function 3
Function 4
…..
User 1
User 2
User 3
…..
4. Use case models – diagrams with specification
Order service system
Supply catalogue
initiates
Check order status
initiates
Client
initiates
uses
Update account
Cancel order
<<include>>
Finance system
initiates
<<include>>
<<include>>
Place order
<<include>>
Update goods quantity
uses
<<include>>
initiates
Sales representative
uses
Collect goods data
Prepare sales report
Warehouse system
<<include>>
initiates
<<include>>
Collect goods from suppliers
uses
Prepare and send ordered products
Delivery company
initiates
Employee
* If the diagram was prepared using PowerDesigner or other design tool and the scenarios are
inside the use cases then the source file should be attached
5. Information structures modeling – class diagram
Member
# Member Number : int
# Member Name
: String
# Member Address : String
+ change Name ()
: void
+ change Address () : void
<<actor>>
Club Member
<<actor>>
Past Member
- Membership expiration Date : Date
Product
#
#
#
#
#
#
Product Number
Quantity In Stock
Product Type
Unit Price
Current Month Units Sold
Current Year Units Sold
:
:
:
:
:
:
String
int
String
Double
int
int
1..1
-
Member Date Of Last Order
Member Phone Number
Member Credit Card Expire Date
Member Credit Card Number
Member Credit Card Type
Member Balance Due
Audio Category Preference
Video Category Preference
Game Category Preference
E-mail Address
Date Enrolled
+
+
+
+
change Phone Number ()
display Balance Due ()
change Preferences ()
add Club Member ()
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Date
String
Date
String
String
Double
String
String
String
String
Date
Agreement
binds
1..1
void
void
void
ClubMember
Agreement Number
Agreement Expire Date
Agreement Active Date
Required Number Of Credits
conducts
Transaction
Transaction
Transaction
Transaction
Transaction
Reference Number
Date
Type
Description
Amount
0..*
Member Ordered Product
Merchandise
-
Merchandise Name
Merchandise Description
Merchandise Type
Unit Of Measure
:
:
:
:
-
String
String
String
String
Quantity Ordered
Quantity Shipped
Purchase Unit Price
Credits Earned
:
:
:
:
places
int
int
Double
int
Return
0..*
0..*
Title
#
#
#
#
#
#
Title Of Work
Title Cover
Catalog Description
Copyright Date
Entertainment Company
Credit Value
:
:
:
:
:
:
String
String
String
Date
String
int
Member Order
0..1
consists of
-
Order Number
: int
Order Creation Date
: Date
Shipping Address Name
: String
Order Sub Total
: Double
Order Sales Tax
: Double
Order Shipping Method
: String
Order Shipping & Handling Cost : Double
Order Prepaid Amount
: Double
Order Prepayment Method
: String
+ change Shipping Method () : void
+ calculate Prepaid Amount () : Double
Video Title
Audio Title
-
Artist
:
Audio Category
:
Number Of Units In Package :
Audio Media Code
:
String
String
int
int
+ add Audio Title () : AudioTitle
-
Producer
Director
Video Category
Language
Video Media Type
Video Encoding
Screen Aspect
:
:
:
:
:
:
:
String
String
String
String
String
String
String
+ add Video Title () : VideoTitle
Game Title
-
String
Date
Date
int
Transaction
#
#
#
#
#
0..*
sold as
:
:
:
:
+ change Expire Date () : void
1..1
1..1
+ change Quantity In Stock ()
: void
+ calculate Current Month Units Sold () : int
+ calculate Year Units Sold ()
: int
1..*
Manufacturer
Game Category
Game Platform
Game Media Type
Number Of Players
:
:
:
:
:
String
String
String
String
int
+ add Game Title () : GameTitle
:
:
:
:
:
int
Date
String
String
Double
6. Interaction models - sequence and communication diagrams
Name of the use case the diagram corresponds to, for example “Making room reservation”
IReservation
:AvailableRooms
:Reservation
Receptionist
1: openReservation
2: checkAvailableRooms
3: displayAvailableRooms
4: insertReservationData
5: makeReservation
6: confirmation
7: closeReservation
8: displayMenu
underneath each sequence diagram a corresponding communication diagram should be placed
:AvailableRooms
3: displayAvailableRooms
2: checkAvailableRooms
8: displayMenu
Receptionist
1: openReservation
4: insertReservationData
IReservation
6: confirmation
7: closeReservation
5: makeReservation
:Reservation
* At least 4 sequence diagrams and 4 corresponding communication diagrams
7. System operation modeling – activity diagrams
Name of the use case the diagram corresponds to, for example “Book rental”
* At least 4 activity diagrams
8. Modeling object classes behavior – statechart diagrams for object classes
Name of the object the diagram corresponds to, for example “States of an EXAM object”
Start
[previous exam session settled]/ plan exam
Created
/ approve
/ edit
Approved
[number of students > 0]/ begin exam
/ cancel
Activated
[exam time is up]/ terminate exam
Terminated
Canceled
/ cancel
/ calculate result
[revocation time is up]/ delete
Settled
[storage time is up]/ delete
Deleted
* At least 3 statechart diagrams
9. System architecture modeling – package diagrams
Settling Orders Parts
Inventory Control
Merchandise trade
Purchases
Forecasting
Sales