1
Q
Explain the reasons for a structured approach to the software development process
A
- increased dependence of many organizations on their computer systems
- Crisis in previous developments: for example: increasing costs of software development, dissatisfaction of users and management with the quality and suitability of software, increasing length and complexity of the software.
- Requirements for standard interfaces, both to users and to other software
- Need for tighter control and management of process, visibility of process, risk management
- Importance of the need for the involvement of end users and management
2
Q
What is the SDLC life cycle?
(Software Development Life Cycle)
A
The Software Development Life Cycle (SDLC) is a structured process that enables the production of high-quality, low-cost software, in the shortest possible production time.
- The goal of the SDLC is to produce superior software that meets and exceeds all customer expectations and demands.
3
Q
What are the SDLC stages?
A
- Project Planning
- Gathering Requirements & Analysis
- Design and Prototype
- Software Development
- Testing
- Deployment
- Maintenance
4
Q
Explain the attributes of a well-engineered software product
A
- Maintainability
- Dependability
- Efficiency
- Usability
- Portability
- Availability of appropriate documentation
5
Q
What is the Waterfall method?
A
The term “waterfall” refers to the flow of the project, where each phase cascades down to the next. It involves a detailed planning phase, execution, testing, and maintenance. And each phase must be completed before moving on to the next, with little to no flexibility for changes during the project.
6
Q
Waterfall method
Advantages:
A
- Provides a way for large or changing teams to work together toward a common goal defined in the requirements phase
- Ensures a disciplined and structured organization
- Provides a simple method to understand, follow, and arrange tasks
- Facilitates management control and departmentalization based on deadlines
- Establishes good coding habits by defining first, then implementing design
- Provides easy access to early system design and specification changes
- Defines milestones and deadlines clearly
7
Q
Waterfall method
Disadvantages:
A
- Design flaws, when discovered, often mean starting over from scratch
- It doesn’t incorporate mid-process feedback from users or clients and makes changes based on results
- Delaying the testing until the end of development is common
- There’s no consideration for error correction
- The model doesn’t accommodate changes, scope adjustments, and updates well
- Work on different phases doesn’t overlap, which reduces the efficiency
- Projects don’t produce a working product until later stages
- Not an ideal model to use for complex and high-risk projects
8
Q
What is rapid prototyping?
A
Rapid prototyping is a design workflow that includes prototyping and testing a design solution with users and stakeholders to help designers and product teams refine and validate ideas quickly.
9
Q
Rapid Prototyping
Advantages:
A
- Explore new concepts and ideas
- Minimize development costs on iterations in the live product (When a feature or product has been validated with users at the design stage, the risk of building something that doesn’t work or isn’t valuable is minimal)
- Market validation
- Testing new features with users
- Getting stakeholder feedback
10
Q
Rapid Prototyping
Disadvantages:
A
- Cost of equipment and technology - 3D printers etc
- Material limitations: The materials used in rapid prototyping may not always match the properties of the final production materials. Which might increase the cost in the design phase.
- Skill requirements: Operating and maintaining the equipment for rapid prototyping requires specialised skills. Companies may need to invest in training or hire skilled professionals to utilise these technologies, effectively increasing overall costs.
- Environmental impact: The materials and processes involved in rapid prototyping, especially in 3D printing, can have environmental implications. Some materials used in 3D printing may need to be more easily recyclable, and the energy consumption of certain rapid prototyping methods can be a concern.
11
Q
What is the Fountain Model/Approach?
A
This model allows for the advancement from (and return to) various stages of software development regardless of whether or not enough tasks have been completed to reach it.
12
Q
Fountain Model/Approach
Advantages
A
- The highly iterative nature of this model ensures intense and frequent customer involvement in the development of the information system.
- The fountain model has the advantage that a progressive piece of software is allowed to be added on each iterative development
- Able to begin coding earlier
- Has many more interaction between design and requirements
13
Q
Fountain Model/Approach
Disadvantages
A
- It may be degraded into a code a bit test a bit which requires frequent iteration and refinement
- Without strong project management, the information system theoretically may never be completed if the project team gets caught in a loop of ever-increasing scope and continuously changing requirements.
- may take more time and cost more to complete the information system.
14
Q
What is the Formal Transformation Approach?
A
This model views software development as a sequence of steps that starts from a formal (mathematical) specification of the requirements and gradually transforms it into an implementation.
15
Q
Formal Transformation Approach
Advantages
A
- It is precise and free of errors (Formal transformation is said to be error-free due to the tedious mathematical specifications which allows no room for errors.)
- It is said to be suitable for safety critical systems. (This is based on its error free nature. Formal transformation ensures that the program or software runs as it is supposed to without any glitches that will affect the running of any vulnerable systems.)
16
Q
Formal Transformation Approach
Disadvantages
A
- It is very costly
- It introduces extra complexity.
- It requires specialized expertise.
(This is so because of its tedious nature.)
17
Q
What is the Reuse-Oriented Approach?
A
an approach to software development that emphasizes the systematic reuse of existing software components to create new applications.
18
Q
Reuse-Oriented Approach
Advantages
A
- lower costs
- faster software development
- save time in testing
- lower risks
-System dependability is increased
- Specialists can be used more effectively by concentrating their expertise on the design of reusable components.
19
Q
Reuse-Oriented Approach
Disadvantages
A
- The more general (and thus reusable) a software component is, the less likely it is to be useful without modification for a given application.
- software reuse can also limit creativity and innovation
- When code is reused from different sources, it can be difficult to ensure that all the components work together effectively, and this can lead to compatibility issues and bugs
20
Q
Analysis Phase
Requirements and Specification Process
What is a Feasibility Study?
A
a project done to determine software’s technical and commercial viability before its development
21
Q
Analysis Phase
Requirements and Specification Process
What is a Requirement Analysis?
A
a process used to determine the needs and expectations of a new product. It involves frequent communication with the stakeholders and end-users of the product to define expectations, resolve conflicts, and document all the key requirements.
22
Q
Analysis Phase
Tools and Techniques
A
- Interviews
- Questionnaire
- Observation
- Review Internal Documents
- Data Flow Diagrams (DFD)
- Entity Relationship Diagram (ERD)
- CASE tools
23
Q
Analysis Phase
Tools and Techniques
What is a Data Flow Diagram?
A
A data flow diagram shows the way information flows through a process or system
- DFDs are built using standardized symbols and notation to describe various entities and their relationships.
24
Q
Analysis Phase
Tools and Techniques
What is a Entity Relationship Diagram?
A
An entity relationship diagram (ERD), also known as an entity relationship model, is a graphical representation that depicts relationships among people, objects, places, concepts or events in an information technology (IT) system.
25
**Analysis** Phase
**Tools and Techniques**
*What are **CASE tools***?
a **software package**that provides support for the design and implementation of information systems.
**C**omputer **A**ided **S**oftware **E**ngineering.
26
**Analysis** Phase
**Tools and Techniques**
*What are **CASE tools Components***?
- Upper Case Tools - Upper CASE tools are used in **planning, analysis and design** stages of SDLC.
- Lower Case Tools - Lower CASE tools are used in **implementation, testing and maintenance.**
- Integrated Case Tools - Integrated CASE tools are helpful in **all the stages of SDLC,** from Requirement gathering to Testing and documentation.
27
**Analysis** Phase
**Tools and Techniques**
*What are **CASE tools Types and Examples***?
- Diagram tools: Flow Chart Maker tool (draw.io)
- Process Modeling Tools: EPF Composer(It allows the capturing of the methods used by your software development team(tasks etc))
- Project Management Tools: Creative Pro Office, Trac Project, Basecamp
- Documentation Tools: Doxygen, DrExplain, Adobe RoboHelp
- Analysis Tools: Accept 360, Accompa, CaseComplete for requirement analysis, Visible Analyst for total analysis.
- Design Tools: Animated Software Design, Blender
- Programming Tools: Eclipse, Replit
- Prototyping Tools: Serena prototype composer, Mockup Builder.
- Web Development Tools: Wix
- Maintenance Tools: Bugzilla for defect tracking, HP Quality Center
28
**Analysis** Phase
**Deliverables**
**Requirement Specification**
*Feasibility Report*
The primary goal of a feasibility study is to assess the **practicality, viability, and potential success** of the proposed software solution.
- type of feasibility study
29
**Analysis** Phase
**Deliverables**
**Requirement Specification**
*Funtional Specification*
A functional specification is a **formal document** used to describe a product's intended **capabilities, appearance, and interactions** with users in detail for software developers. The functional specification is a kind of **guideline** and continuing reference point as the developers write the programming code.
Functional requirements form the behavior of the product.
30
**Analysis** Phase
**Deliverables**
**Requirement Specification**
*Non-Funtional Specification*
a set of specifications that describe the system's operation capabilities and constraints. These are basically the requirements that outline how well it operates, including things like **speed, security, reliability, data integrity**, etc
31
**Analysis** Phase
**Deliverables**
**Requirement Specification**
*What is the difference between Functional and Non-Funtional Specification*?
- Functional requirements explain how the system **must** work, while non functional requirements explain how the system **should perform**.
- Functional requirements form the behavior of the product.
- Non-functional requirements describe the general software characteristics.
- FR explain “What the system does.”
- NFR explain “How the system works.”
32
**Design** Phase
**Design Process**
*Achritectual Design*
the process of **defining** a collection of hardware *and*software components and their interfaces to establish the **framework** for the development of a computer system
33
**Design** Phase
**Design Process**
*Interface Design*
the process designers use to build interfaces in software or computerized devices, focusing on **looks or style**
e.g. voice-controlled interfaces.
34
**Design** Phase
**Design Process**
*Data Structure Design*
The process of **development and organization** of data structures that can effectively **store, manipulate, and retrieve** data in a computer program or system
eg. graphs, hash tables, trees, arrays, linked tables
35
**Design** Phase
**Design Process**
*Algorithm Design*
a process that involves creating a *^step-by-step procedure** or set of instructions for a computer to follow while performing a task or solving a problem
eg. tying your shoelaces
36
**Design** Phase
**Tools and Techniques**
*Structure Charts*
a chart which shows the **breakdown** of a system to its **lowest manageable levels.** They are used in structured programming to arrange program modules into a **tree.** Each module is represented by a **box**, which contains the **module's name.**
37
**Design** Phase
**Tools and Techniques**
*HIPO Charts*
- **H**ierarchical **I**nput **P**rocess **O**utput.
HIPO diagram assesses the system and facilitates documentation. It organizes the software system's modules into a **hierarchy**. HIPO diagrams can be used to get a high-level picture of the system's **functions**
38
**Design** Phase
**Design Methods**
*top-down*
starts with the **general concept** and repeatedly **breaks it down** into its **component parts.** In other words, it starts with the abstract and continually subdivides it until it reaches the **specific.**
39
**Design** Phase
**Design Methods**
*bottom-up*
The bottom-up approach starts with the **low-level details** of the system, such as the **data structures, the algorithms, and the interfaces**. Then, these details are combined and integrated into larger components, and so on, until the whole system is built.
40
**Design** Phase
**Design Methods**
*System Structuring*
The system is decomposed into several. principal sub-systems and communications, between these sub-systems are identified.
(sub-systems,modules,programs)
41
**Design** Phase
**Design Strategies**
*Functional vs Object Oriented*
- OOP is about creating objects and making them interact to build applications. It models software based on real-world objects.
- FP is about creating functions and combining them to solve problems. It models software based on mathematical functions and transformations.
- In essence, OOP is like assembling a machine from different parts, each with its own responsibilities, while FP is like applying a series of mathematical operations to data to achieve a result.
- They belong to two different paradigms: oo is imperative (your code tells how) while functional is declarative (your code tells what, the compiler figures out the how).
42
**Design** Phase
*Guidelines for screens, reports, user interfaces*
1. Visibility of System Status
2. System Match to the Real World
3. User Control and Freedom
4. Consistency and Standards
5. Error Prevention
6. Recognition rather than Recall
7. Flexibility and Efficiency of Use
8. Aesthetic and Minimalist Design
9. Help Users Recognize, Diagnose and Recover from Errors
43
**Design** Phase
**Deliverables**
*System Architecture*
Software architecture is, simply, the **organization of a system.** This organization includes all components, how they **interact** with each other, the **environment** in which they operate, and the **principles** used to **design** the software. In many cases, it can also include the evolution of the software into the future.
44
**Design** Phase
**Deliverables**
*Design Specification*
Specifically, the software design specification is a description of the **software components and sub-systems** to be provided as part of the product.
45
**Validation** Phase
*Need for the Testing Process*
- Helps in saving money
- Security
- Quality of the product
- Satisfaction of the customer
- Enhancing the development process
- Easy while adding new features
- Determining the performance of the software
46
**Validation** Phase
*Test Plans*
a detailed and comprehensive software testing document that outlines the **strategy, objectives, schedule, resources, and overall approach** that are needed to complete a project.
- In many ways, a test plan is like a blueprint for a building.
47
**Validation** Phase
*Software Inspection*
to a peer review of software to identify **bugs or defects** at the *early* stages of SDLC.
- It is a formal review that ensures the documentation produced during a given stage is **consistent** with **previous stages** and conforms to preestablished rules and standards.
48
**Validation** Phase
**Software Testing**
*Unit Inspection/Testing*
The main goal of unit testing is to ensure that **each** unit of the software performs as intended and meets requirements. Unit tests help make sure that software is working as expected before it is released.
- example: a function that adds two integers and returns the sum as the output. A unit test code will look like, If the function returns anything other than 30, then it means the test case fails, and there is some issue with the code.
49
**Validation** Phase
**Software Testing**
*Acceptance Test*
software testing that evaluates whether a system meets its **business and user requirements**. It is the **final testing** stage before a system is released to production. The main purpose of acceptance testing is to verify that a system: Meets all of its **functional *and* non-functional** requirements.
50
**Validation** Phase
**Software Testing**
*Test Case Design*
a specific set of steps that will exercise a **particular functionality** within the software. Each test case should have a **clear expected result** so that you can determine whether or not the software is functioning as intended.
eg.
1. Check response when valid email and password is entered
2. Test the Data
3. Perform actions
51
What is **Alpha testing**?
Small internal group of developers looking for bugs
52
What is **Beta testing**?
Larger group of external testers looking for UI/Functionality Issues
53
What is **White Box testing**?
allows the tester to see and know the code that is being tested which gives them the ability to pinpoint errors to be fixed
- it is done by developers
54
What is **Black Box testing**?
does not internal the internal workings of a he code. It is normally done by alpha/beta testers to give feedback
55
**Functional** vs **Non-Functional** Requirements
Functional-
the things or processes that the system should be able to do when completed. eg. Display records
Non-functional-
the constraints that the system may have eg. fast runtime
Bee’s CAPE Space
flashcards
Decks in class (20)
# Cards
-
Types of ventures: Entrep mod 1150
-
Com Sci mod 125
-
Risk and Benefits: Entrep mod 13
-
Caribbean studies: definitions of the Caribbean21
-
Caribbean studies: Society and Culture9
-
Historical Process CARIB STUDIES24
-
Examples of natural disasters: Caribbean Studies10
-
Revision Caribbean2
-
Com Sci mod 255
-
MOB Forecasting28
-
Com Sci mod 378
-
MOB Inventory Management16
-
MOB Production Methods9
-
MOB Costing22
-
MOB Capacity Planning13
-
MOB Quality4
-
MOB Product design12
-
MOB Productivity4
-
Legal and Regulatory Framework: Entrep Mod 12
-
Digital media0
