Lecture Notes 2 Flashcards by Unknown Unknown

What are the 4 phases of software engineering?

REQUIREMENTS ANALYSIS
SYSTEM DESIGN
VALIDATION
EVOLUTION

How well did you know this?

Not at all

Perfectly

The task communicating with customers and users to determine what
their requirements are. This is sometimes called Requirements Gathering.

Eliciting Requirements

How well did you know this?

Not at all

Perfectly

Determining whether the stated requirements are unclear, incomplete,
ambiguous, or contradictory, and then resolved these issues.

Analyzing Requirements

How well did you know this?

Not at all

Perfectly

Requirements might be documented in various forms, such as natural-
language documents, use cases, user stories, or process specifications.

Recording Requirements

How well did you know this?

Not at all

Perfectly

High-level abstract requirements written as statements, in a natural language
plus diagrams, of what services the system is expected to provide to system users and the constraints under which it must operate.

User Requirements

How well did you know this?

Not at all

Perfectly

A user shall be able to search the
appointments lists for all clinics.

Search Appointment

How well did you know this?

Not at all

Perfectly

Two kinds of requirements based on the intended purpose and target
audience:

User Requirements
System Requirements

How well did you know this?

Not at all

Perfectly

detailed description of what the system should do including the software system’s
functions, services, and operational constraints.

System Requirements-

How well did you know this?

Not at all

Perfectly

REQUIREMENT Analysis includes three types of activity:

Eliciting Requirements
Analyzing Requirements
Recording Requirements

How well did you know this?

Not at all

Perfectly

The study considers whether the proposed system
will be cost-effective from a business point of view.

Feasibility Study

How well did you know this?

Not at all

Perfectly

An estimate of whether the identified user needs may be satisfied using current software and hardware technologies.

Feasibility Study

How well did you know this?

Not at all

Perfectly

product features or functions that developers must
implement to enable users to accomplish their tasks

Functional Requirements

How well did you know this?

Not at all

Perfectly

describe what the system should do.

Functional Requirements

How well did you know this?

Not at all

Perfectly

what are the 2 examples of Functional Requirements?

Search Appointment
Generate Reports

How well did you know this?

Not at all

Perfectly

How well did you know this?

Not at all

Perfectly

The system shall generate each day, for
each clinic, a list of patients who are expected to attend
appointments that day.

Generate Reports

How well did you know this?

Not at all

Perfectly

The system allows the user to create account.

Create Account

How well did you know this?

Not at all

Perfectly

The system allows the user to search books based on title,
publication, etc. and find their location in the library.

How well did you know this?

Not at all

Perfectly

The system allows the user to view the list of books available

View

How well did you know this?

Not at all

Perfectly

The system can print/generate reports such as list of books, list of
borrowers, etc.

Generate Reports

How well did you know this?

Not at all

Perfectly

Specify the characteristics of the system as a whole.

Non- Functional Requirements

How well did you know this?

Not at all

Perfectly

a set of specifications that describe the system’s
operational capabilities and constraints and attempt to
improve its functionality.

Non- Functional Requirements

How well did you know this?

Not at all

Perfectly

More often more critical than individual functional
requirements.

Non- Functional Requirements

How well did you know this?

Not at all

Perfectly

EXAMPLES OF Non- Functional Requirements

Reliability, response time

How well did you know this?

Not at all

Perfectly

If NFRs not addressed properly, the results can include: * Users, clients, and developers are unsatisfied. * Inconsistent software. * Time and cost overrun to fix the software which was prepared without keeping NFRs in mind.

TRUE

The user-interface should be simple enough for everyone to understand the system.

Usability

The data stored about books and the fines calculated should be correct, consistent, and reliable.

Accuracy

The software should be easily maintainable and adding new features and making changes to the software must be as simple as possible.

Maintainability

* It is the process of defining the elements of a system such as the architecture, modules and components, the different interfaces of those components and the data that goes through that system.

SYSTEM DESIGN

Systems design implies a systematic approach to the design of a system.

SYSTEM DESIGN

* It is meant to satisfy specific needs and requirements of a business or organization through the engineering of a coherent and well-running system

SYSTEM DESIGN

It may take a bottom-up or top-down approach, but either way the process is systematic wherein it takes into account all related variables of the system that needs to be created—from the architecture to the required hardware and software, right down to the data and how it travels and transforms throughout its travel through the system.

SYSTEM DESIGN

4 types of SYSTEM DESIGN

Architectural Design Interface Design Component Design Database Design

Where you identify the overall structure of the system

Architectural Design

Where you define the interfaces between system components.

Interface Design

Where you design the system data structures and how these are to be presented in a database.

Database Design

Also called “Software Validation and Verification”

Validation

refers to the process of determining whether or not the products of a given phase of a software development process fulfill the process established during the previous phase.

Validation

Where you take each system component and design how it will operate.

Component Design

refers to the process of evaluating software at the end of its development to ensure that it is free from failures and complies with its requirements.

Validation

is defined as an incorrect product behavior.

failure

are we building the product right

VERIFICATION

Software V&V Approaches

Software Technical Reviews Software Testing Proof of Correctness Simulation and Prototyping Requirements Tracing

checks if the product functions are what the customer really wants

Validation

* are we building the right product?

Validation

-Each component is tested independently without the other sub systems.

Development Testing

3 STAGES IN THE TESTING PROCESS

1. Development Testing 2. System Testing 3. Acceptance Testing/Alpha Testing

checks if the products meet the requirements definition

VERIFICATION

-Components may be simple entities such as functions, objects, or classes

Development Testing

the test team knows exactly how the software behaves

Alpha testing

-Concerned with finding errors that result from unanticipated interactions between components and component interface problems.

System Testing

-Concerned with showing that the system meets its functional and non- functional requirements

System Testing

is the final internal acceptance testing for your software.

Alpha testing

May reveal errors and omissions in system requirements definitions

Acceptance Testing/Alpha Testing

it ensures that your software is bug-free, stable, and functioning as expected

Alpha testing

it aims to test every single user flow end to end

Alpha testing

PEOPLE IN THE DEVELOPMENT

1. Development Team 2. End – users

The process of developing a software product using software engineering principles and methods is referred to as software evolution.

evolution

a white boxQ testing

Alpha testing

Understands the system

Analyst

starts from the requirement gathering process.

evolution

The process of developing a software product using software engineering principles and methods is referred to as _____ evolution.

software evolution

evolution processes include:

Change Request Impact Analysis Release Planning System Update System Release

This includes the initial development of software and its maintenance and updates, till desired software product is developed, which satisfies the expected requirements.

evolution

After which developers create a prototype and show it to the users for their feedback at the early stage of software development.

evolution

responsible in making the software

1. Development Team

The users suggest changes, on which several consecutive updates and maintenance keep on changing.

evolution

Build/create the software.

1. Development Team

Defines the software architecture, components, modules, interfaces.

System Designer

write codes of the system in a specific programming language

Programmer

* Directly Involved in the system

* Operational Job * Supervisor * Executive

reviews faults and errors of the system

Tester

Development Team

Analyst System Designer Programmer Tester

- if it is fit for use

Software Quality

used/ utilize the system

2. End – users

part of quality management focused on providing confidence that quality requirements will be fulfilled.(ISO 9000)

* Quality Assurance (QA)

* Performs the daily task/operation of the organization * Concern: How does it work?

* Operational Job

* Performs supervisory job * Concern: Physical Interface & Performance

* Supervisor

Indirectly Involved in the system

* Quality Assurance (QA)

- errors and faults found during the SE process

* dev’t team

* Provides finances and initiatives * Outputs/results * Concern: global view of the system

* Executive

groups and external organizations which set standards to be followed

* Quality Assurance (QA)

ability to evolved and adopt change over time.

Maintainability

- is the total characteristics of an entity to satisfy stated and implied needs .

Quality

Three Perspectives of Software qUALITY

Quality of the Product Quality of the Process Quality in the context of System Environment

capability to use resources efficiently.

Efficiency

- in terms of products/services provided by the business in which the software is used.

Quality in the Context of business Environment

- relative to the person analyzing quality.

Quality of the Product

- failures of task are avoided - system development process is improved

Quality of the Process

- if it gives what they want and when they want it, all the time.

*end-users

ensures that the software product complies with user requirements and standards.

SOFTWARE QUALITY ASSURANCE

- software adds value to the business

Quality in the Context of business Environment

Characteristics of a well-engineered Software

* Usability * Portability * Reusability * Maintainability * Dependability * Efficiency

ease with which the user communicates with the system

Usability

capability of the software to execute in different platforms.

Portability

ability to transfer from one system to another

Reusability

characteristics of the software to be reliable, secure, and safe.

Dependability

1. Respect your teammates, even when you disagree or they are wrong. 2. Accept group decision even when you disagree. 3. You must include all group members in decisions. 4. You should do your best to contribute to your team. 5. Email or text is not a good medium for resolving problems.

INTERPERSONAL COMMUNICATION RULES