Solved by verified expert:Type: Individual ProjectUnit: Detailed Design PracticesDeliverable Length: 7–10 pages Assignment DescriptionFor the overall final project, you had to select 1 project from 3 different organizational software design projects, which included the following:Client/server designProject Web-based designSales user interface design project.With an understanding of the existing requirements review process, expected software design models, the software solution design, expected software specifications, and the requirements for the new software design project selected, you must now address the validation and verification of the design being proposed.Provide a description of the organization, schedule, resources, responsibilities, tools, techniques, and methodologies to be deployed to perform the verification and validation activities of your design. This should be the last section of your overall project.Provide the following consolidated Design Implementation Proposal to include the appended V&V plan due this week:Provide the details of the Implementation Proposal Executive Summary to include the following:Introduction to the implementation proposalSystem objectives and constraintsSystem functional requirements to capture the intended behavior of the system expressed as services, tasks, or functionsThree use cases based on the unified modeling language (UML) 2.0 required to identify the set of interactions happening between the intended actors and the softwareSystem design summary description to reveal the intended software designSequence diagrams to transition from the use cases and requirements to system object interactions captured in sequences needed for refinementUpdate a requirements traceability matrix that depicts how requirements are satisfied during the design phase of the software development life cycleV&V PlanDesign summaryPlease submit your assignment.
unit_4_individual_project_software_design.docx
Unformatted Attachment Preview
1
Software Design (CS457 – 1802A – 01)
Unit 4 Individual Project
Phillip Isiah Houston Sr.
Instructor Howard Evans
Due Date 05 May 2018
2
UML Development Practices
Introduction
The primary role of a sequence diagram focuses on the explanation of the system in
development more deeply. The programmer’s design an events diagram in such a way that it
helps the targeted audience to perceive the inner workings of the system in context. Without the
sequence diagram, the users may not see and understand the messages sent from one module to
the other. Mostly, the developers build a sequence diagram after the completion of an activity
one. The role of the activity diagram focuses on the definition of the various actors and their
roles in a system. The diagram shows the interaction between the various actors and their kind of
access to the system`s resources. As a result, it helps in the development of the system forming
its principles on the overall level of access and the kind of interaction each actor may undertake.
Mostly, the design of the sequence diagram forms its principles from the activity diagram.
However, the former does not include the different actors, but instead, it shows the kind of
messages that it may deal with during the overall operations.
The user, in this case, represents the entire team of actors who may include either a single
or multiple parties. The sequence diagram shows the overall interaction between an actor and the
business system outlining the various tasks that each party perform and their respective messages
(Yang, Yu, Sun & Qian, 2012). Mostly, the developers make use of the sequence diagram to
show not only the various players in the process but also the kind of messages and returns that
each of them performs. In the case of a client-server model, its good representation may include
the banking system. From the details and activity diagram provided in the previous paper, this
section will focus on the evaluation and representation of the banking system while taking into
account the interaction among the user, the money dispensing machine and also the institution
3
itself. Before the sequence proceeds, the user and the system must switch on. No transaction may
happen with a switched off the system. The design of the sequence diagram happens after the
development of an activity one. The figure below diagram shows the sequence diagram of a
banking system outlining the primary messages sent to the various events.
Sequence diagrams
4
5
6
Postcondition
In the first initiation of the process, the first instance includes the setup between the user
and the system. The user initiates the process by inserting an ATM card. The system in the first
place requests the user to insert the ATM card to perform a given task. After the user inserts the
card, the system requests him or her to key in the correct passcode. This scenario as described
assumes that the user keys in the correct pin code to the system to access the various services
offered by the institution. The next step involves the system interacting with the bank so as to
verify and validate the submitted access codes. The bank administrator then checks to see if the
user keys in the correct access codes after inserting the card. This situation includes the user
interacting with the bank with the intentions of getting cash through the withdrawal function.
The following step happens after the bank verifies the access codes submitted by the user.
Subsequently, this gives the user access to the system where s/he may undertake his or her
respective tasks.
In the next step, the user then after getting access to the system selects an option. Before
selecting a given option as per his/her desires, the system first displays the available services as
well as products. Therefore, this allows the user to view the available options on the system
which plays a crucial role in fostering decision making. The user or in this case, the actor selects
the desired option from a wide range as displayed by the system. After selecting a given a
choice, the system checks to verify that the user keys in the correct details. This verification must
go hand in hand with the system parameters. The user, therefore, may not enter or request for an
invalid option. Since the primary goal of the user involves requesting for cash from the ATM, the
dispenser submits the request to the main system that controls all the banking activities for
7
further scrutiny. In case the bank finds out that the user in context requested a larger amount of
money that the one s/he already owns, it returns an error message. However, this scenario
assumes that the user owns a considerable amount of money enough to transact. At this point, the
system then continues to validate the request presented by the user. In the end, the system
dispenses cash as per the user requirements. Since the user may need additional transactions, he
or she may request the system to process other requests. Otherwise, it proceeds to terminate the
entire process. The final stage includes the system printing a receipt showing the activities of the
transaction. The change occurs to both the system and the user after giving out the cash and
updating the account balance.
8
References
Yang, N., Yu, H., Sun, H., & Qian, Z. (2012). Modeling UML sequence diagrams using
extended Petri nets. Telecommunication Systems, 51(2-3), 147-158.
…
Purchase answer to see full
attachment
