System Design Specification

Question 1

Derives from a comprehensive blueprint in creating software; this includes a software’s details with its functionality, development timeline, and goals.

Answer 1

System Design Specifications document (SDS)

Question 2

Also focuses on the idea that security, maintainability, usability and reliability must be aligned with this and with the use of stories, use cases and data models to ensure a comprehensive design.

Answer 2

Nonfunctional requirements

Question 3

KEY PEOPLE IN THE DESIGN PROCESS

Answer 3

Software Architects
System Designers
UI/UX Designers
Database Architects

Question 4

They define the overall system architecture and make high-level design decisions.

Answer 4

Software Architects

Question 5

They translate architectural concepts into detailed system designs, ensuring alignment with architectural principles.

Answer 5

System Designers

Question 6

They focus on the user interface and experience, designing layouts and elements to enhance usability.

Answer 6

UI/UX Designers

Question 7

They handle the system’s database architecture, defining data models and optimizing performance.

Answer 7

Database Architects

Question 8

STEPS IN CREATING DESIGN SPECIFICATIONS

Answer 8

1. Understand the Requirements
2. Identify Design Constraints
3. Define Quality Attributes
4. Identify Control Classes
5. Develop Sequence Diagrams
6. Document Design Decisions
7. Review and Iterate
8. Finalize the Design Specifications
9. Maintain Traceability

Question 9

STEPS IN CREATING DESIGN SPECIFICATIONS

It is crucial to understand the project requirements before
diving into design specifications.

Answer 9

Understand the Requirements

Question 10

STEPS IN CREATING DESIGN SPECIFICATIONS

Analyze any design constraints, including technology stack, platform compatibility, budget, and existing architectural patterns.

Answer 10

Identify Design Constraints

Question 11

STEPS IN CREATING DESIGN SPECIFICATIONS

Secure, reliable, maintainable, and usable features should be identified and prioritized.

Answer 11

Define Quality Attributes

Question 12

STEPS IN CREATING DESIGN SPECIFICATIONS

Coordinate interactions between components and enforce business rules.

Answer 12

Identify Control Classes

Question 13

STEPS IN CREATING DESIGN SPECIFICATIONS

Using user stories or use cases, in creating this diagrams to illustrate how classes interact and how actions flow within the system.

Answer 13

Develop Sequence Diagrams

Question 14

STEPS IN CREATING DESIGN SPECIFICATIONS

By maintaining this documentation, future references can be made and stakeholders can be kept informed about the progress of the project.

Answer 14

Document Design Decisions

Question 15

STEPS IN CREATING DESIGN SPECIFICATIONS

Review design specifications with stakeholders, ensuring alignment with requirements and feasibility, and iterate based on feedback for necessary adjustments.

Answer 15

Review and Iterate

Question 16

STEPS IN CREATING DESIGN SPECIFICATIONS

It should be comprehensive enough to guide the implementation phase, but should also be flexible enough to adapt to changes in requirements or constraints as they arise

Answer 16

Finalize the Design Specifications

Question 17

STEPS IN CREATING DESIGN SPECIFICATIONS

To ensure alignment between the implemented system and the intended design, between design specifications and requirements

Answer 17

Maintain Traceability

Question 18

Serves as the final plan in developing a system. It must include as much information as possible as it serves as the guideline for the developers, testers, and other professionals in the later stages of SDLC.

Answer 18

System Design Specifications (SDS)

Question 19

The following information can be found in the SDS:

Note that the SDS do not exactly have all these information and
varies depending on the system being developed and the business it serves

Answer 19

Business Rules and Requirements
Scope of the Project
People Involved
Work and Task Assignments
Features and Functionalities
Interface Design
Timetables and Schedule

Costs
Possible Issues and Solutions
Priority Levels
Models, Diagrams, and Charts
Architecture and Module details
Algorithms and Pseudocode
Testing Plans

Question 20

There are several methods of presenting information to enhance clarity and communication with people in the next stages of the development life cycle. It is a help in having an organized and stable workflow for developers and testers.

Answer 20

VISUAL AIDS IN SYSTEM DESIGN

Question 21

What are some of the Visual Aids in System Design?

Answer 21

1. Design Specifications Table
2. Wireframes
3. Use Case Diagram
4. Activity Diagram
5. Class Diagram
6. Physical Database Model

Question 22

for organizing requirements and specifications in a tabular format.

Answer 22

Design Specifications Table

Question 23

Drawn for planning the UI design of a system. Guides the UI developers to avoid redesigns in the interface.

Answer 23

Wireframes

Question 24

Used to depict the users’ interactions with the system. Important to use if there are different types of users with different accessible functionalities

Answer 24

Use Case Diagram

Question 25

Also known as an object-oriented flowchart, this diagram is used to model behaviors within the system. Used when there are multiple objects perceived in the system with multiple interactions with each other.

Answer 25

Activity Diagram

Question 26

Used to organize multiple classes in an object-oriented system. The attributes, methods and relationships between classes are depicted in this diagram. Bears similarities to a logical database model.

Answer 26

Class Diagram

Question 27

Used to model how the actual database architecture must look like. Includes the settings such as data type, key type, null allowed, etc.

Answer 27

Physical Database Model