OZES Analysis Report: Agile Development, Use Case Diagrams, User-Centered Design, and Human Computer Interaction

1
OZES ANALYSIS REPORT
Contents
1. Consultation........................................................................................................... 4
1.1. Agile development.............................................................................................. 4
1.1.1. Extreme Programming.................................................................................4
1.1.2. Scrum....................................................................................................... 4
1.1.3. Feature driven development..........................................................................5
1.1.4. Rational Unified Process............................................................................... 5
1.2. The recommendation.......................................................................................... 5
2. The Analysis........................................................................................................... 6
2.1. The information system event table.......................................................................6
2.2. The Use Case Diagrams...................................................................................... 8
2.3. The Uses Case Descriptions..................................................................................9
2.4. The domain model class diagram........................................................................12
2.5. The design class diagrams.................................................................................13
3. The memo............................................................................................................. 13
3.1. User-Centered Design....................................................................................... 13
3.2. Human Computer Interaction............................................................................ 14
References............................................................................................................... 15

2
Table of Figures
Figure 1: use case for sell item system......................................................................8
Figure 2:use case for CRM.......................................................................................... 8
Figure 3: use case for delivery................................................................................... 9
Figure 4: domain class diagram for information system...........................................12
Figure 5: broker class............................................................................................... 13
Figure 6: order class................................................................................................. 13

3
Table of Tables
Table 1: event table for the information system........................................................6
Table 2: making and canceling order.........................................................................9
Table 3:posting items............................................................................................... 10
Table 4: generating report on sales..........................................................................10
Table 5: posting selling offers...................................................................................11

4
OZES ANALYSIS REPORT
1. Consultation
1.1. Agile development
Agile systems development is an approach to systems development that involve users in the development
process due to stakeholder’s need to change functional requirements and also promotes fast, adaptive, and
continual rapid delivery , planning and improvement respectively.
The agile approach also presents an iterative development where software development phases (plan,
analysis, design, develop and test, integration) are repeated for each delivery or change in requirements.
The four agile methods focused on in this discussion are discussed below.
1.1.1. Extreme Programming
Extreme programming focusses on the degree of quality improvement of a software product as the
stakeholder requirements change in the process. There are a number of roles of people who participate in
this approach such as the couch, tester, tracker and the customers themselves.
Extreme programming has values one should focus on while developing a system using this approach
such as communication between participants, simplicity and preciseness of requirements, courage to not
harm your teammates, respect to one another, and feedback from participants
Pros
 Reduces time and cost of software development hence fast software delivery
 Understandable code is produced by developers
 Immediate user feedback due to users’ involvement
 Accountability and transparency is highly expressed by developers
Cons
 Design is neglected since the approach focuses on coding
 Quality control and assurance is not focused on
 Different geographical location of different programmers and users is not supported
1.1.2. Scrum
Scrum approach is an agile method used to manage the process of software development and the
deliverables produced by each phase in the process. It involves having a sprint master who manages the
meetings and reviews done on deliverables. It also involve a backlog that contains all the requirements
and a sprint that usually is a two weeks’ time for developing an item from the backlog. The requirements
are also put on story cards.
Pros
 It increases revenue since cost and time for marketing is reduced
 Development is easy
 High flexibility due to user involvement