SOFTWARE DESIGN AND ENGINEERING -- Module 2

Modeling Tools

• Unified Modeling Language (UML) — Lucidchart, Visual Paradigm

• Entity-Relationship Diagram (ERD) tools — MySQL, dbdiagram

• Flowchart tools — Draw.io, Microsoft Visio

Prototyping Tools

Tools such as Figma, Adobe XD, Axure RP, and Sketch

Testing/Debugging Tools

Tools such as Selenium, Postman, jUnit

Standards

Official documents that ensure reliability

Standards

Defines requirements, specifications, and guidelines, developed through consensus by national or international bodies

Standards

Set the minimum accepted professional practice or quality

ISO/IEC 25010

Standard for system and software quality models

ISO/IEC 122207

Standards for software lifecycle processes

ISO/IEC 27001

Standards for information security management

IEEE 830-1998

Recommended practice for software requirements specification

IEEE 1016-2009

Recommended practice for software design descriptions

IEEE 1471-2000

Architecture description of software-intensive system.

NOTE: was suspended by ISO/IEC 42010

Style Guides

Promotes consistency and readability in coding (ex. Google Java Style Guide)

Linting Tools

Automatically checks code for style and potential issues (ex. Pylint)

Open Web Application Security Project (OWASP)

Security standard that provides guidelines for secure software development

National Institute of Standards and Technology

Security standard that offers various cybersecurity frameworks and standards

Engineering Constraints

Rules or limits that engineers follow when designing/building. These rules can be related to time, money, technology, etc.

Time Constraints

Constraint wherein time is limited. Tackles deadlines and time-to-market considerations

Budget Constraints

Constraints on resources and funding

Resource Constraints

Constrains on human resources (developers, etc.), hardware, software, and other resources

Scope Constraints

Limitations on the features and functionalities included in the software. Balancing it with available resources and project objectives

Quality Constraints

Constraints on performance, reliability, and usability. It makes sure the software maintains a certain level of quality

Security Constrains

Compliance with security standards and protocols

Business Requirement Specification (BRS)

In the SDLC planning and requirements phase this is prepared after planning.

Software Requirement Specification (SRS)

A document based on the BSR that is created during the Analysis phase

Software Requirement Specification (SRS)

Consists of all the product requirements to be designed and developed during the project

1. Functional Requirement Specification

2. System Requirement Specification

2 documents based on the SRS that is still created during the Analysis Phase

Design Document Specification (DDS)

A document created during the Designing Phase that is based on the requirements specified in the SRS

Design Document Specification (DDS)

Helps in coding for accomplishing the project without much hassle