System Analysis and Design

The main goal of this paper is to discuss the methodology for agile development of OZES company and at the end the paper will provide a memo.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student:
Name of the University:
Author Note

1
SYSTEM ANALYSIS AND DESIGN
Executive summary:
The main goal of this paper is to discuss the methodology for agile development of OZES
company and at the end the paper will provide a memo.

2
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Methodology:.............................................................................................................................3
Event Table................................................................................................................................6
Use Case Diagram......................................................................................................................7
Use Case Description.................................................................................................................9
Domain Model Class Diagram.................................................................................................10
Design Class Diagram..............................................................................................................11
Bibliography.............................................................................................................................16

3
SYSTEM ANALYSIS AND DESIGN
Methodology:
Extreme programming:
 Discussions: extreme programming is a popular agile development methodology that
follows principles such as involvement of consumers at high level and also promotes
involvement between developers and consumers and this makes this methodology
extremely consumer focused and also interactive as well. This method might hence
might be considered for the OZES management team as they have very little
knowledge about the agile process which might require for the team and management
to be involved with the project right from the development of the information system
 Advantages: development of project with close association with the client and this is
what require for the OZES management team as this will provide various stakeholders
and team members from the OZES management team to conceptualise the system
right from the beginning of the system development and therefore it will make it
easier for them to execute various functions of the system for managing business
process effectively which include storing important business data regarding
consumers, sales and then allowing brokers to access those information without
compromising the security of the data
 Disadvantages: although this agile method allows for extensive consumer
involvement, it is a highly disciplined method and it requires project associates that
are well versed with agile principles. However, lack of agile culture in OZES
organization, this method is not consistent with organizational culture of OZES and it
is not recommended for OZES team and management

4
SYSTEM ANALYSIS AND DESIGN
Scrum:
 Discussions: this method is most widely used for agile software development. Here in
this method product owner is in control of the project iteration. The developer team
follows the iteration and project is executed in that sequence according to the
prioritization defined by the product owner. Each project iteration is known as sprint
and these sprint are mostly of 30 days duration
 Advantages: scrum provides full control to product owner and hence this will allow
OZES to execute the system development according the way they like it to develop
within the duration they want the project to be completed
 Disadvantages: if product owner is not well versed with the project development
through agile method, it is most likely that the schedule developed by the team will
not be proper and it might lead to scope creep and project creep which might lead to
overall project delay with increase in project cost. Hence, this method for OZES
might be risky to adopt for developing the information system for their business
process
Lean development:
 Discussions: it is a software development methodology in agile software
development where the main focus is optimization of efficiency and minimization
of waste.
 Advantages: lean development method simplifies the project development process
and thus helps to reduce various aspects that increases project complexity. Hence,
application of this methodology for developing CRM system is an effective choice
for OZES

5
SYSTEM ANALYSIS AND DESIGN
 Disadvantages: the project requires extensive involvement of team member and
success of the project depends on each of the team members. However, lean
development allows to outsource project development if organization does not
have required expertise for developing the project and this is the case with OZES
team and this is where lean development methodology is an effective choice for
CRM system development
Adaptive software development:
 Discussions: the adaptive system development methodology is one of the popular
agile development methodology and the main principle of this method is faster
development and software evaluation
 Advantages: the fast nature of this method allows to develop system with less time
and it integrates evaluation of the software while development of the software is being
executed. Therefore this method is suitable for companies who want faster product
development without compromising in the quality of the software
 Disadvantage: agile method provides faster project execution, but the organization
should have proper infrastructure which is consistent with this principle and
organizational culture plays an important role in this context. However, OZES has not
conducted any previous project with agile method and they have not enough
experience in this regard as well therefore it is not suitable for them to develop the
CRM system with this method
Recommendation:
According to this discussion, it is clear that each method has its own advantages and
disadvantages. CRM system development is traditionally complex process and requires
effective project planning with adequate details for each of the strategy deployed for the

6
SYSTEM ANALYSIS AND DESIGN
project. However, focus should be such that detailing for project planning does not include
information which is not relevant to the project planning and project execution to ensure that
project is not affected with information overflow. In this respect, lean development is an
excellent choice for CRM development.
Event Table
The event table is a table of data that helps the users for storing, retrieving as well as
processing the events within a table database such as the structure. The table is designed for
utilizing the cases where the events are required to be extracted from the stream as well as
accumulated over a huge period for the later batch or the real time processing. In the window
that are predefined, the event table might be having more sophisticated strong as well as the
criteria that is retrieval. An event table may be utilized in the SiddhiQL expressions. The
event table is given below.
Event Trigger Source Use Case Response Destinatio
n
Place
Advertisement
Uploading
Advertisement
Brokers Advertisement Contact Customers
Contact
Organization
Place a phone
call
Customer Make Call Display
Questionnaire
System
Answer the
questionnaire
Submit the
Questionnaire
Customer Provide
Details
Request
reference
information
System
Provide
reference
Advertiser
ID / Reference
ID
Customer Provide
Reference
Store the
Details
System

7
SYSTEM ANALYSIS AND DESIGN
Sell items Post
Advertisement
Brokers Sell-second
hand Items
Display to
customer
Customer
Purchase Item Place a
purchase
request
Customer Purchase Process
Purchase
System
Receive Items Deposition by
OZES
Staffs Item
Deposition
Pack Items System
Send Items Packing and
sending
Staffs Send Items Send to the
customer
Customer
Send mails Item sold System Send Mails Access
details
Broker
Make
Payment
Receive Items Customer Receive
Payment
Process
broker
payment
System
Broker
Payment
Make
Payment
System Broker
Payment
Receive
payment
Broker
Use Case Diagram
A use case diagram is a behaviour or dynamic diagram within the UML. The
functionality of the systems by utilizing the use cases and actors can be modelled by the use
case diagram. The use cases are some set of the services, functions as well as the actions that
is needed by the systems to perform. It can be stated that a system is a thing that can be
operated or developed like a web site. In the use case diagram the actor are the entities or

8
SYSTEM ANALYSIS AND DESIGN
people who have been operating under the roles that are defined in the system. The use case
diagram is as follows:

9
SYSTEM ANALYSIS AND DESIGN

10
SYSTEM ANALYSIS AND DESIGN
On the above use case diagram, there are four actors, they are the staffs, customers, system
and the associated broker. The connection between the actors have been provided in the use
case diagram.
Use Case Description
The use case description can list the steps that are involved for completing the use
case with the flow of the tools of the events. The flows of the events are one of the most
critical elements of any of the use case description. The software that are based on the use
case with the event tools that are powerful and also having the support of the wireframe
editing, referencing and the extended flow that have been included in the use case as well as
introducing the logic of the business with loop and the if-then-use operators. The activity
diagram and the system level sequence diagram can be generated by the users from the event
flow for utilizing in the system design ideas that are related to communication. The table of
the use case diagram is provided below.
Name Sell-second hand item
ID 6
Description The broker would be selling the second hand item to the customers.
The customers would watch the advertisement, and the view the
products in the system. They would be able to proceed with the
purchase after the processing of the advertisement.
Actors The actors of the system are Brokers and Customers. The system also
acts here as a secondary actor for the use case.
Triggers The process is triggered after the advertisement is posted by the
broker.
Pre-condition Advertisement

11
SYSTEM ANALYSIS AND DESIGN
Post-condition Make Purchase
Flow of process Actor System
1. Send advertisement
2. Sell Second-hand item
3. Make Purchase
1. Post Advertisement
2. Display item to customer
3. Sell Item
Exceptions Exceptions take place if the advertisement does not reach out to the
customer.
Domain Model Class Diagram
In software engineering, the domain model class diagram is one of the conceptual of
one particular domain which can incorporate both the data as well as the behaviour. The
domain model class diagram is a system that is related to the abstractions which is able to
describe the aspects of the knowledge sphere that are selected, the activity or influence. Then
the domain model can be utilized for solving the problems and the issues that are related to
the particular domain. The domain model class diagram is the representation of concepts that
are meaningful of the real world and pertinent to that domain which are required to be
modelled within the software. This domain model class diagram naturally utilizes the
vocabulary of one particular domain. This might not refer to any implementations that are
from the technical field like the components of the software or the database which needs to be
designed. The domain class diagram is given below.

12
SYSTEM ANALYSIS AND DESIGN
Design Class Diagram
With the completion of the interaction diagram for the realizations of the use case,
there is the possibility for identifying the specifications for the classes of the software which
can be take part in the solution for the software as well as annotate them with the detail
design like the methods. The design class diagrams are created usually with the diagrams that
are known as the interaction diagram. Most of the method names, relationships as well as
classes can be sketched out in the designing part through applying the patterns that are related
to the responsibility assignment. Though this is possible as well as desirable for doing the
small interaction in the diagram. The example of the design class diagram is given below.

13
SYSTEM ANALYSIS AND DESIGN
In this diagram the broker id, phone number, payment, date has been taken as integer and on
the other side the broker name, address and the detail has been taken as the string.

14
SYSTEM ANALYSIS AND DESIGN

15
SYSTEM ANALYSIS AND DESIGN
Memo
To: CEO, OZES
From: Enterprise Software Developer
CC: CEO, Enterprise Software Developer
Date: Please fill
Re: Evaluation of UCD and HCI
Adopting a User Centred Design (UCD) approach
Background:
Currently there is not a strong reliance from OZES on computers to get their work done
outside standard applications. Therefore, acceptance of the new system is a concern for the
management team and therefore it is required for setting a plan for the development of the
Human Computer Interaction (HCI) for developing the CRM application for the organization.
Purpose:
According to the requirements of the organization, a brief memorandum is developed
commenting on adopting a User Centred Design (UCD) approach and setting a plan for the
development of the Human Computer Interaction (HCI) when considering the CRM
application. This memo briefly discuss UCD and HCI in general and investigate the
implications of adopting a UCD for OZES for system development.
Description of UCD:
User centred design is a design method which considers requirements of the users in each
phase of the project development and integrates those requirements with the system
development. Here the whole system is designed from user perspective and hence allows
developer to have better control on users requirements and users satisfaction. However, this

16
SYSTEM ANALYSIS AND DESIGN
design process require that the users are involved throughout the project execution and they
need to share their feedback with proper knowledge of the feature which they are evaluating.
Hence it is required to ensure that users have proper knowledge about the feature because
based on the review and feedback, developers decide if specific feature of the system should
be modified or not so that it is consistent with user requirements and their satisfaction for the
system. Hence, user centred design is effective for ensuring enhanced user satisfaction
through system development.
Description of HCI:
The human centered design is considered is a specific type of design and a framework for
management which is utilized for development of the solution of some problem by the
involvement of the human perspective in each of the steps for the solving of the problem. In
this case the main reason of human involvement is observation of problems within the
context conceptualizing, brainstorming, implementing and developing of a particular type of
solution.
Implication of HCI in CRM development process:
Human centred design promotes human perspective in the context of problem solving process
and thus simulates the way a human might solve a specific problem through a system. When
this design process is CRM development, it will help it to ensure that team members and
stakeholders of OZES who requires to execute the system for storing, processing and
accessing business data is required to do it with efficiency as human centred design approach
will help in identifying issue in this context and thus it will help developer to design the
system exactly the way OZES would have liked it to be designed so that it is easier for them
to execute various functionalities of the system for various business purposes.

17
SYSTEM ANALYSIS AND DESIGN
Bibliography
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Alexandros, N.K., Sakas, D.P., Vlachos, D.S. and Dimitrios, N.K., 2017. Comparing scrum
and xp agile methodologies using dynamic simulation modeling. In Strategic Innovative
Marketing (pp. 391-397). Springer, Cham.
Cabot, J., Clarisó, R. and Riera, D., 2014. On the verification of UML/OCL class diagrams
using constraint programming. Journal of Systems and Software, 93, pp.1-23.
Cooper, R., 2017. Supply chain development for the lean enterprise: interorganizational cost
management. Routledge.
Cooper, R.G., 2016. Agile–Stage-Gate Hybrids: The Next Stage for Product Development
Blending Agile and Stage-Gate methods can provide flexibility, speed, and improved
communication in new-product development. Research-Technology Management, 59(1),
pp.21-29.
Cunha, Alcino, Ana Garis, and Daniel Riesco. "Translating between Alloy specifications and
UML class diagrams annotated with OCL." Software & Systems Modeling 14, no. 1 (2015):
5-25.
Kniberg, H., 2015. Scrum and XP from the Trenches. Lulu. com.
Kumar, S., Luthra, S., Govindan, K., Kumar, N. and Haleem, A., 2016. Barriers in green lean
six sigma product development process: an ISM approach. Production Planning &
Control, 27(7-8), pp.604-620.

18
SYSTEM ANALYSIS AND DESIGN
Lindsjørn, Y., Sjøberg, D.I., Dingsøyr, T., Bergersen, G.R. and Dybå, T., 2016. Teamwork
quality and project success in software development: A survey of agile development
teams. Journal of Systems and Software, 122, pp.274-286.
Matharu, G.S., Mishra, A., Singh, H. and Upadhyay, P., 2015. Empirical study of agile
software development methodologies: A comparative analysis. ACM SIGSOFT Software
Engineering Notes, 40(1), pp.1-6.
Petre, M., 2013, May. UML in practice. In 2013 35th International Conference on Software
Engineering (ICSE) (pp. 722-731). IEEE.
Rolland, K., Dingsoyr, T., Fitzgerald, B. and Stol, K.J., 2016. Problematizing agile in the
large: alternative assumptions for large-scale agile development. In 39th International
Conference on Information Systems. Association for Information Systems (AIS).
Vijayasarathy, L.R. and Butler, C.W., 2015. Choice of software development methodologies:
Do organizational, project, and team characteristics matter?. IEEE software, 33(5), pp.86-94.