20

Software Design Specification (SDS) Document

Tramain
Vivid Wo
2/25/201
 1

CIS 421: Software Engineering

Assignment 5: Software Design Specification (SDS) Document

Name: Tramaine Banks

February 25, 2019

Instructor: Professor Daniel Brown

 2

Table of Contents
Title Page……….…………………………………………………………….…………………..1
Table of Contents…………………………….………………………………….………………..2
Executive Summary………………………………………………………………………………3
Introduction…………………..…………………………………………………………………...4
Scope……………………….……………………………………………………………………..4
Detailed system Design and Data Flow Diagrams………………………………………………..4

Sequence Diagram ………………………………………………………………………………..5

System Key Contributors and the Primary and Secondary Keys…..……………………………..5
Detailed Breakdown of Various Functions………………………………………………………..6
Detailed Breakdown of the 3 Tier Levels Architecture.…………………………………………..7
Detailed Breakdown of Various Functions of Attributes/Actors...………………………………..8
List of Additional Attributes and or Actors...……………………………………………………..9
Creation of the System’s Database Library.……………………………………………………..10
The Final and Full Cycle of the Vivid World Inc Project………………………………………..10
The Final and Full Cycle of the Markup.….……………………………………………………..11
The Complete and Final Visual Processes.………………..……………………………………..11
User Interface.……………………………………………..……………………………………..12
Summary of Project Deliverables.………………..………………………….…………………..15
Assumptions……………………………………………………………………………………...15
Risk………………………………………………………………………………………………16
Requirements…………………………………………………………………………………….16
Reference………….……………………………………………………………………………..17
 3

Executive Summary
The name of this company is the “Vivid World Inc.” Which is an online shopping
experience that is of high quality, cheaper to purchase, faster and reliable, we sale various
products such as apparel, accessories, electronics, and so along. In summation, we will have
suppliers worldwide to our customers. The “Vivid World Inc.” company will offer a three to
five-day delivery of any product that we sale online through our web portal as well as our
shipping fee will be low priced. Likewise, Vivid World will allow its consumers the comfort of
an approachable means of buying several products. Moreover, we will constantly place our
customers first by making sound choices for our business as well as engage in the subject. By the
way, our mission for Vivid World to give our clients a safe and easy means of accessing our
online shopping portal at a reasonable price of any of their selections from our web portal. In
addition, we will provide excellent working conditions to all our employees, increase teamwork
and camaraderie while creating multiple job opportunity while fulfilling our civic duty.
Furthermore, this firm’s vision is to change the world through online buying of fashion and so
on, which will be accomplished one customer at a time as well by transcending online shopping
in an innovative way.
Nevertheless, the “Vivid World Inc. “ will sale products online by being linked to our
clients via our web portal like that of Amazon. In addition, we will use a custom-built database
that will house all client and product information and entities. Also, this will be driven through a
parent child relationship database comprised of various tables from our web portal. Furthermore,
the said structure will be developed by a defined in a Sequence Diagram. The Vivid World’s Inc.
will breakdown their project structure by organizing the projects functional areas into sections
that will address all their task to be completed and achieve a valid structure of the overall
solutions functionality. Also, the WBS chart project will practice at a functional level to
gradually achieve functionality of all features in the new system.
Next, Vivid World Inc. will be implementing an Application Server, which would provide
the application’s logic layer in the “Vivid World” system’s three- tier architecture by enabling the
client components the ability to interact with its data resources as well as its legacy applications.
Also, the three-tier architecture will be comprised of programming models, which will allow the
distribution of application functionality across three independent systems.
Last, the user interface design part of the “Vivid World” system would address and focus
on forecasting what the users/clients may need to do. Likewise, the user interface design phase of
this project will ensure that the interface has elements such as ease of use as well as being easy to
access, understand, and use to facilitate various actions. Moreover, the “Vivid World” system
will design a user interface (UI), which would interface without there being a conflict of interest
somewhere along the line. For example, by trying to make the interface pleasing to the eye,
functionality and ease of use might be impaired. So, by defining and creating a good user
interface it must allow the user an efficient and effective means of interaction.
 4

1.0: Introduction

Let me start, by introducing our firm which called “Vivid World Inc. “and we will sale

products online by being linked to our clients via our web portal like that of Amazon. In addition,

we will have a database that will house all client and product information entities as well as this

will be driven through a parent child relationship of tables that will make of the overall database

portal. Furthermore, the said structure will be developed as well as the names will be defined in a

Sequence Diagram, which is generally used by developers as well as it will be used to model the

interactions between objects in a single use case.

Last, the Vivid World’s Inc. work breakdown structure will be that of organizing the

project by functional areas to section all task to be completed and to achieve a valid structure that

will outline the overall solutions functionality. Nevertheless, our WBS chart project will be

practiced at a functional level to break down the overall functionality and on an assignment, level

to break down both the functionality and the functions needed to fulfill the feature.

2.0: Scope

Detailed system Design and Data Flow Diagrams

Let’s define the Project Scope which is the part of project planning that encompasses

being decisive as well as documenting the said it listing of specific project goals, deliverables,

tasks, costs and deadlines. The scope will use the Sequence Diagram to explain how the different

parts of this system will interact with each other to carry out a specific function. Also, it will

handle the order of how the interactions will occur while specific uses are executed. For instance,

it is also used to display to show the different parts of a system work in a ‘sequential manner to

get a task completed.

 5

Sequence diagram for each entity, also called Interactive workflows.

Diagram1: Sequence Diagram

Furthermore, there will be a breakdown of three types of Interaction diagrams such as: 1)

Sequence diagrams, 2) Communication diagrams, and 3) Timing diagrams. Likewise, the three

diagrams in question will be used to illustrate interactions between parts within a the “Vivid

World” system. Moreover, between the three sequence diagrams being used the preferred

diagram to be used by both developers as well as the readers comparably will be that of the

sequence diagram, communication diagram, and the timing diagrams due to their simplicity and

ease of use.
 6

Diagram 2: Key Contributors and the Primary and Secondary Keys of the system

and their functions.

Diagram 3: Detailed Breakdown of Various Functions listed Previously

Also, the WBS can be used as a means of distributing the work load to be accomplished as

well as planning the design to implement the solution. Likewise, the project manager as well as

various team members will need to document and provide detail information about all the

deliverables identified and agreed upon in the project scope in an afford to meet all the

stakeholders demands.

Next, Vivid World Inc. will implement an Application Server, which would provide the

application’s logic layer in the “Vivid World” system’s three- tier architecture by enabling the

client components the ability to interact with its data resources as well as its legacy applications.

Likewise, together this three-tier architecture will be comprised of programming models that will
 7

allow and enable the distribution of application functionality across three independent systems,

which are as follows:

 The “Tier One” of the architecture is the “Client Components”, which will be

running on local workstations.

 The “Tier Two” of the architecture is the “Processes”, which are running on the

remote servers.

 Last, the “Tier Three” of the architecture is the as such:

1) Discrete Collection of databases,

2) Resource managers, and

3) Mainframe applications (IBM, (2018).

Diagram 4: Detailed Breakdown of the 3 Tier Levels Architecture

Moreover, we created a diagram of each outline of the three tier levels architecture and the

functions of each layer. Also, all three tiers will be logical, however, they would be implemented

to not be run on the same physical server as well as to run on the same server, which is

dependent on how the network environment is setup (IBM, (2018).

 8

Each one our customers has a different unique ID and is connected to precisely one

account. Our account maintains a shopping cart and orders. The consumer could register as a

web user to be able to order products online. A customer is not required to be a web user because

shopping could also be done by a smartphone or by ordering from online categories. Web user

has login name which also serves as a unique id. Web user could be in different states, country,

working, and be connected to a shopping cart.

Diagram 5 A & B: Detailed Breakdown of Various Functions of Attributes/Actors

Furthermore, after the objects have been identified, then we will write each detailed

description of each use case and its functions. Furthermore, with each of the description we will

be allowed to easily figure out the interactions that will be needed in the sequence diagram. Also,
 9

this would define what is to transpire between the objects identified above when the use case has

been executed. In addition, we have provided the steps that will transpire with each of the use

case named ‘Create New User Account’ and “Create New Product ID”.

 The User request the system to create a new online account

 The User request the system to create a new product ID account

 The Admin then selects the specified user account type

 The Admin enters the user’s details

 The user’s details are checked using the user Credentials Database

 The new user account is created

 A summary of the of the new account’s details are then emailed to the user

 The same steps apply to the create new product ID account

Moreover, the defined Attributes and or Actors would be that of the following:

List of Additional Attributes and or Actors:

 Admin

 User Account

 Product ID

 Online Product Management system

 User credentials database

 Email system
 10

Diagram 6: Creation of the System’s Database Library (which is the Foundation)

Diagram 7: The Final and Full Cycle of the Vivid World Inc Project

Moreover, the different patterns provide in all three diagram seven, eight and nine

diagrams will be used by the stakeholder to choose various technologies suitable for their

different concerns and in general, helps design loosely coupled systems. Each interest, in theory,
 11

can be replaced or evolved separately from others, which is hard or even impossible in tightly

coupled systems. Also, MVC is implemented as necessary, and this is where frameworks in

pretty much all the languages vary. Some structures provide the MVC separation, but in doing

so, will lock you into their way of separating the concerns. So, you are restricted by what these

frames do, which may or may not be a good thing. Some other contexts let you choose different

parts as necessary so that you can substitute one with the other. “Whenever a user makes any

request from the controller, it contacts the appropriate model which returns a data representation

of whatever the user requested. This model will be the same for a particular task and or

irrespective of how we wish to display it to the user. That is why we can choose any available

view to render the model data” (Mathur, 2018).

Diagram 8: The Final and Full Cycle of the Markup for the Vivid World Inc Project
 12

Diagram 9: The Complete and Final Visual Processes

For instance, note that this project’s goal is to utilize this plan and designs for the website

to help this organization to retrieve obtain and advertise to a boarder online customer base as

well as to draw some additional business partners/associates to the company from the site. We

are creating a better delivery option on the consumer's smartphone to where they can track their

package when it's sent out, estimated time, and drop off. The notification on the application will

inform the buyer anywhere and anytime of the day. Also, if the client wants to pick up their

package or packages personally, the app will notify the user the area what Amazon drop box is

located. Our cloud-based CRM systems will give the company faster efficient understanding of

our consumers because it allows immediate and broader access to the customer relationship

management database. “Category creation in any product is usually about creating something

that doesn’t exist. When Steve Jobs created the iPad, it was a new category. But when the iPhone

came out, it combined existing categories. In the enterprise space, and as buyers of software, we

have buyers and organization’s structured and wired to think if they’re in a customer support

team, they need to buy contact center software. If they’re in the sales team, they need CRM, and

if they’re in marketing, they need marketing automation” (Cameron, 2018).

User interface diagram

 13

Diagr

am 10: User Interface (N.d., (2017)

The user interface design part of the “Vivid World” system would address and focus on
forecasting what the users/clients may need to do. Also, the user interface design phase of this
project will ensure that the interface has elements such as ease of use as well as being easy to
access, understand, and use to facilitate various actions. Likewise, the user interface phase of the
“Vivid World” project will convey some organized concepts such as: 1) interaction design, 2)
visual design, and 3) information architecture (N.d., (2014).
Next, the “Vivid World” system would select their Interface Elements for the users to use
to familiarize themselves with the interface elements. Nevertheless, in this phase of the “Vivid
World” system would attempt to be consistent and predictable in their choices and that of their
layout (N.d., (2014). Also, this would aide in the users ease of task completion, efficiency, and
satisfaction, which would be inclusive of the following interface elements, such as:
 Input Controls: buttons, text fields, checkboxes, radio buttons, dropdown lists, list
boxes, toggles, date field
 Navigational Components: breadcrumb, slider, search field, pagination, slider, tags,
icons
 Informational Components: tooltips, icons, progress bar, notifications, message boxes,
modal windows
 Containers: accordion (N.d., (2014)
Furthermore, ‘Vivid World” system will be designing a decent user interface (UI), which
would interface without there being a conflict of interest somewhere along the line. For
example, by trying to make the interface pleasing to the eye, functionality and ease of use
might be impaired. So, by defining and creating a good user interface it must allow the user
an efficient and effective means of interaction. Also, the designs most work in the
 14

background to allow and the users to complete their tasks with ease of use (N.d., (2014). In
addition, we have listed some additional design aspects to further enhance the “Vivid World”
system design interface model and they are as listed:
 Keep the interface simple. The best interfaces are almost invisible to the user. They

avoid unnecessary elements and are clear in the language they use on labels and in

messaging.

 Create consistency and use common UI elements. By using common elements in your

UI, users feel more comfortable and can get things done more quickly. It is also

important to create patterns in language, layout and design throughout the site to help

facilitate efficiency. Once a user learns how to do something, they should be able to

transfer that skill to other parts of the site.

 Be purposeful in page layout. Consider the spatial relationships between items on the

page and structure the page based on importance. Careful placement of items can help

draw attention to the most important pieces of information and can aid scanning and

readability.

 Strategically use color and texture. You can direct attention toward or redirect attention

away from items using color, light, contrast, and texture to your advantage.

 Use typography to create hierarchy and clarity. Carefully consider how you use

typeface. Different sizes, fonts, and arrangement of the text to help increase scan ability,

legibility and readability.

 Make sure that the system communicates what’s happening. Always inform your

users of location, actions, changes in state, or errors. The use of various UI elements to

communicate status and, if necessary, next steps can reduce frustration for your user

(N.d., (2019, Feb 9th).

 15

Think about the defaults. By carefully thinking about and anticipating the goals people bring to

your site, you can create defaults that reduce the burden on the user. This becomes particularly

important when it comes to form design where you might have an opportunity to have some

fields pre-chosen or filled out (N. d., 2019).

Last, Vivid World Inc. will present and have the final sign off with all of the stakeholders

and make sure that they have an overall understanding of the project as well as its inter

functionalities before signing and approving each final deliverable to make sure that all resources

or needed as well as to eliminate the existing of possible scope creep in the project at any given

time, which is very important due to the additional cost and labor, which is important

(Alexander, 2018). Also, we will be providing various graphs, diagrams and charts to define each

areas functionality.

Summary of Project Deliverables:

1. Survey: We would survey any current consultants and or clients to help determine

any desired features and or content needed for the intranet site.

2. Files needed for any templates to be used when the system is being first

implemented. Also, the project team will decide and select the initial templates

based on the initial surveys.

3. Examples of all completed templates.

4. Instructions for using project management tools.

5. Example application tools.

6. Articles

7. Links

8. Expert database
 16

9. User request features

10. Site design

11. Test the plan

12. Project benefit measurement plan

Assumptions:

1. Lack of input from consultants

2. Lack of input from client presentative

3. Security of the new system

4. Providing a efficient search feature

5. Effectively promoting the new system

6. Realizing the benefits of the new system

7. Having a good communications plan in place

8. Meeting all deadlines on time

9. All documentation has been kept updated

10. Software and hardware will address all the project’s needs.

11. No cause of scope creep

Risk:

1. Inadequate planning

2. Absence of leadership

3. Poor cost estimates

4. Poor time estimates

5. Over or Under Budgeting

 17

Requirements:

1. Documentation the overall project.

2. Creating the WBS of the project.

3. Defining, verifying, and controlling the scope of the project.

4. Addressing any and all software and hardware needs.

5. Website design: site map, graphic design, and programs

6. Home page design: text, images, and hyperlinks

7. Marketing pages: text, images, and hyperlinks.

8. Sales pages: text, images, and hyperlinks

9. Meet the stakeholders needs, requirements, and deadlines.

10. Stay in budget to avoid scope creep.

References:
Alexander, M. (2018, May 23). How to meet project goals by creating a work breakdown
structure. Retrieved from https://www.techrepublic.com/article/how-to-meet-project-
goals-by-creating-a-work-breakdown-structure/
Cameron, N. (2018, August 22). Fresh Works CEO: Why we think we can win at
customer engagement management. Retrieved from
https://www.cmo.com.au/article/645505/freshworks-ceo-why-we-think-we-can-win-
customer-engagement-management/
IBM (2018, August), IBM Knowledge – WebSphere Application Server Overview: Three
– tier architectures, Retrieved from site:
https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websph
ere.nd.multiplatform.doc/ae/covr_3-tier.html
Mathur, A. (2018, April 9). A Beginner’s Guide to MVC Architecture in Java. Retrieved
from https://www.upgrad.com/blog/mvc-architecture-in-java/
N.d., (2014), Argon Design: 5 aspects of a good user interface, Retrieved from site:
http://www.argondesign.com/news/2014/feb/5/5-aspects-good-user-interface/
N.d., 2018, June 22nd, Sequence Diagram Tutorial: Complete Guide with Examples,
Retrieved from site: https://creately.com/blog/diagrams/sequence-diagram-tutorial/
 18

N.d., (2017), User Interface Design, Retrieved from site:

https://en.wikipedia.org/wiki/User_interface_design#/media/File:Linux_kernel_INPUT_OU
PUT_evdev_gem_USB_framebuffer.svg

N. d., 2019, February 9, User Interface Design Basics

, Retrieved from site: https://www.usability.gov/what-and-why/user-interface-
design.html
N.d., (2018, August), IBM Knowledge – WebSphere Application Server Overview:
Three – tier architectures, Retrieved from site:
https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.
multiplatform.doc/ae/covr_3-tier.html
N.d., (2017), User Interface Design, Retrieved from site:
https://en.wikipedia.org/wiki/User_interface_design#/media/File:Linux_kernel_INPUT_OU
PUT_evdev_gem_USB_framebuffer.svg

N.d., (2018, August), IBM Knowledge – WebSphere Application Server Overview:

Three – tier architectures, Retrieved from site:
https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.
multiplatform.doc/ae/covr_3-tier.html
N.d., 2018, June 22nd, Sequence Diagram Tutorial: Complete Guide with Examples,
Retrieved from site: h
ttps://creately.com/blog/diagrams/sequence-diagram-tutorial/
N. d., 2019, February 9, User Interface Design Basics, Retrieved from site:
https://www.usability.gov/what-and-why/user-interface-design.html
N.d., 2018, June 22nd, Sequence Diagram Tutorial: Complete Guide with Examples,
Retrieved from site: https://creately.com/blog/diagrams/sequence-diagram-tutorial/