1/63
Vocabulary flashcards covering core topics in Software Engineering, Software Life Cycles, Software Process Models, and Unified Modeling Language (UML) structural and behavioral concepts.
Software (Pressman/US Definition)
(1) Instructions (computer programs) that when executed provide desired features, function, and performance; (2) data structures that enable the programs to adequately manipulate information; and (3) documents that describe the operation and use of the programs.
Software Engineering (Schach/Europe Definition)
A discipline whose aim is the production of fault-free software, delivered on time and within budget, that satisfies the client’s needs, and remains easy to modify when user needs change.
Application Software
Software with Spreadsheets, Databases, Word processors, Internet Browsers, and Computer Games.
System Software
Software with The Operating system and Utilities.
Hardware
CPU, disks, mouse, printer etc.
Embedded Software
software when its part of another device, or sensors on a car.
Product-line Software
A set of software-intensive systems that share a common, managed set of features satisfying specific needs of a particular market segment or mission, developed from core assets in a prescribed way. Like fast food.
Web-Application Software
A web application or web app is any application software that runs in a web browser and is created in a browser-supported programming language (such as the combination of JavaScript, HTML and CSS) and relies on a web browser to render the application. Content in Web Interface and Hypercosm Applet, and the Software is web browser and Hypercosm Player.
AI Software
Software technologies that make a computer or robot perform equal to or better than normal human computational ability in accuracy, capacity, and speed.
Engineering
the application of science and mathematics by which the properties of matter and the sources of energy in nature are made useful to man in structures, machines, products, systems, and processes. - Boehm (1979)
the profession in which knowledge of the mathematical and natural sciences gained by study, experience, and practice, is applied with judgment to develop ways to use, economically, the materials and forces of nature for the benefit of mankind. - ABET
Software Life Cycle
-First Stage: Feasibility— 1. Feasibility, 2. Market Analysis
-Second Stage: Requirement Engineering— 1. Requirements, 2. Requirements Elicitation, 3. Domain Analysis, 4. Requirement Specification (Rec. Spec.)
-Third Stage: Planning— 1. Project Planning, 2. Cost analysis, 3. Scheduling, 4. Software Quality Assurance, 5. Work-Breakdown Structure.
-Fourth Stage: Design— 1. Architecture Design, 2. User-Interface Design, 3. Detailed Design
-Fifth Stage : Implementation— 1. Coding
-Sixth Stage: Testing— 1. Unit Testing, 2. Integration Testing, 3. System Testing, 4. Alpha Testing, 5. Beta testing, 6. Acceptance testing, 7. Regression testing, …
-Seventh Stage: Operation and Maintenance— 1. Delivery, 2. Installation, 3. Training, 4. Help Desk, 5. Maintenance
Milestones
Events in the software life cycle (such as completing a user manual) used to assess project progress and status.
Feasibility Study
The 1st stage in the software life cycle focused on determining if a proposed software development project is worthwhile.
Requirement Analysis
The 2nd stage of life cycle for the system’s services, constraints, and goals are established by consultation with system users. What will it do??? So define in detail and serve as a system specification.
Requirements
1st part of the 2nd stage of life cycle, The designer and customer try to capture a description of ‘what’ the eventual system will be expected to provide.
Requirement Elicitation
2nd part of the 2nd stage of life cycle, The process of obtaining requirements from system users and gathering details about the domain/environment in which the final product will function.
Planning stage
The 3rd stage of life cycle is determining how to develop the software. Cost Analysis is when we determine cost estimates. After that, scheduling, so layout the development in a timeline. This includes concept, prototype, refine & redesigns, Software development, manual and installation guide, pre-release activities, and meeting activities. Then there’s Software Quality Assurance (SQA).
Architectural Design
The 1st step of 4th life stage (Design Stage), this type designing is High-level functional decomposition of a software system into separate components to enable isolated development and independent integration. The structure.
Detailed Design
The 3rd step of 4th life stage (Design Stage), this type is designing the algorithms for the individual parts, take components (class name, attributes, methods) then take every function, then write a clear description for it.
Alpha Testing
The 4th part of the 6th stage of life cycle, Software testing conducted by the customer at the developer’s site.
Beta Testing
The 5th part of the 6th stage of life cycle, Software testing conducted by the customer at the customer’s operational site.
Regression Testing
The 7th part of the 6th stage of life cycle, Saving and re-running tests from previous program versions to ensure that the new version retains existing capabilities without introducing defects.
A Process
A series of steps involving activities, constraints, and resources that produce an intended output of some kind. It involves a set of tools and techniques.
Code-and-Fix Process Model
A life-cycle approach where a product is implemented without prior requirements, specifications, or design, and reworked repeatedly until client satisfaction. This is where that 46% failure comes from. Implemented without requirements or specifications, or any attempt at design.
Waterfall Model
A classic life cycle process suggesting a systematic, sequential approach to software development flowing through requirements, planning, modeling, construction, and deployment.

V-Process Model
A variation of the waterfall model depicting how quality assurance testing actions directly map to communication, modeling, and early construction phases.
Increment Process Model
An incremental process model combines elements of the waterfall model applied in an iterative fashion. The incremental model applies linear sequences in a staggered fashion as calendar time progresses. Each linear sequence produces deliverable “increments” of the software. By the time (RE) 3 begins, there is planning 2 and Design 1 going on simultaneously.

Rapid Application Development (RAD)
An incremental process model emphasizing a short development cycle through heavy use of component-based construction, capable of building functional systems in 60 to 90 proposal days. (RE) up to 100%, then Planning at 100%. With Design, coding, and testing splitting into different parallel modules (d1 in module 1, cd2 in module 2…dn, cn, tn in module n). Or some just split design and coding up to meet altogether and do Testing then finally Deployment. It develops the software with multiple teams.


Spiral Model
An evolutionary process model coupling the iterative nature of prototyping with the controlled aspects of the waterfall model, driven by systematic risk analysis during each pass. Core software has the basic functions as a working product, with increment 1, 2, to the final increment (modifications/features) to complete software. This is a quick way to debut a product quickly and patch/update it later. Spiral Model will start with RE, then planning, designing, that goes coding, and testing. Then loop around 3 to several more times with a product to assure each time we come again to another step, we spend more time with each step every run around. Quality is improved every time.
Unified Modeling Language (UML)
A standardized (ISO/IEC 19501:2005) general-purpose visual modeling language with graphic notations used to specify, visualize, design, and document software systems. NOT A SOFTWARE DEVELOPMENT PROCESS.
Static View (UML)
A perspective in UML modeling that emphasizes structural architecture using objects, attributes, operations, and relationships to document required system components.
Dynamic View (UML)
A perspective in UML modeling that emphasizes dynamic behavior by showing object collaborations and changes to internal object states over time.
UML Structural Diagrams
Shows the static structure of the system and its parts on different abstraction and implementation levels and how they are related to each other. The elements represent the meaningful concepts of a system. Ex. Class, Component, Composite Structure, Deployment, Object, Package, Profile Diagrams.
Class Diagram
MOST WIDELY USED (Structural Diagram), to find what info to collect, shows the structure of the software, this diagram defines the classes (students, instructor, course), attributes for each classes (characteristics/variables, and functions/methods), and the relationship between each class (all 3 with students, instructor and course), class is modeled in three sections of a rectangle TOP(class name), Middle (attributes), and Bottom (Operations) with visibility symbols (public (+), private(-), protected(#), and package(~)) and used for conceptual modeling (have the external view/schema of characters, how it creates a conceptual view/schema, and finally physical view/schema), detail modeling and data modeling.
Component Diagram
Describes how a software system is split up into components and shows the dependencies among these components. (Structural Diagram)
Composite Structure Diagram
Describes the internal structure of a specific class and the collaborations that this structure makes possible, gas pedal—>engine—>transmission—wheels. (Structural Diagram)
Deployment Diagram
For software installers, shows architecture of the system as distribution of software artifacts to deployment targets, describes the hardware used in system implementations and the execution environments and artifacts deployed on the hardware. (Structural Diagram)
Object Diagram
Shows a complete or partial view of the structure of an example modeled system at a specific time. (Structural Diagram)
Package Diagram
Describes how a system is split up into logical groupings by showing the dependencies among these groupings and their definitions. Inside a project/software, is two packages, inside of each are classes, which carry methods and data in them. (Structural Diagram)
Profile Diagram
Describes lightweight extension mechanism to the UML by defining custom stereotypes, tagged values, and constraints. (computer’ software, the memory, vendor, CPU in the server, and metaclass). (Structural Diagram)
UML Behavioral Diagrams
Shows the dynamic behavior of the objects in a system, which can be described as a series of changes to the system over time. Ex. Activity, Communication, Interaction Overview, Sequence, UML State Machine, Timing, Use Case Diagrams.
Activity Diagram
Describes the business and operational step-by-step workflows of components in a system, the overall flow of control. (Behavioral Diagram)
Communication Diagram
Shows the interactions between objects or part in terms of sequenced messages. Like function calls and methods to describing both static structure and dynamic behavior of a system. (Behavioral Diagram) Ex: A client machine requests verification from server machines, server machines have an authentication module for secondary verification for a valid user and OTP, then return to client machine module
Interaction Overview Diagram
Provide overview of the flow of control where nodes of the flow are interactions or interaction uses. (Behavioral Diagram)
Sequence Diagram
Widely used, shows how objects communicate with each other in terms of a sequence of messages, also indicates the lifespans of objects relative to those messages, like a schedule. (Behavioral Diagram)
UML State Machine Diagram
Describes the states and state transition of the system. Ex. (Password & user id for login—>index, if password or user id fails—>redirect command back). (Behavioral Diagram)
Timing Diagram
A special form of UML sequence behavioral diagram with reversed axes, placing lifelines in vertical compartments to focus explicitly on object behaviors under timing constraints.
Use Case Diagram
another widely used (Behavioral Diagram) describes the functionality provided by a system in terms of actors, their goals represented as use cases, and any dependencies among those use cases. (Course registration system (course offering) (registration) (Add course) (Late registration) (Drop course) (Grade submission) (Grade approval), list the people using (student, dept chair, register, instructor) the cases with each part)

UML Member Visibility Notations
Symbols placed before a class attribute or method name specifying access control: + for Public, # for Protected, - for Private, and ~ for Package.
UML Relationships
Association, Aggregation, Composition, Generalization, Realization, Dependency
Association
A class connected to each other by a line that holds attributes and operations pertaining directly to the relationship between two classes. Ex. student < teaches < Teacher
Association constraints
Dashed line signifies the stipulation constraints. Ex. University student > registered > CSC 280 - - - canvas access. If not registered, no canvas access.
Multiplicity
* = many. Ex. College 1 — *students.
Qualifier/Qualified Associations
An identifier attribute enclosed in a small rectangle adjoining the 'one' side class in a one-to-many relationship, used to lookup specific associated objects. Ex. {passenger}—[booking]{flight}
![<p>An identifier attribute enclosed in a small rectangle adjoining the 'one' side class in a one-to-many relationship, used to lookup specific associated objects. Ex. {passenger}—[booking]{flight}</p>](https://assets.knowt.com/pdf-flow-prod/582c3515-876b-4078-beac-9e52ac9e8961-figures/8.jpg)
Bi-Directional (STANDARD) Association
both parties are aware of each other, solid lines, with multiplicity (how many), association name (who is doing what for who), and role (who works for who).
Uni-Directional Association
Only one class knows the relationship. Have multiplicity and role name for known class. A single arrow pointing one direction, like overdrawn account report—>bank account, since the bank doesn’t know of the relationship.
Aggregation and Composition
a class is formed by collecting other classes (Ex: players, coaches, and staff make —<> TEAM
Reflexive Association
Class in association with itself. With car 1—0…4 passenger, with car, there should be different relationship with driver 1–-drives—>0..4 passenger. Or with employee class (1 manager—*staff)
Aggregation
A 'has a' relationship formed when a class represents a collection or assembly of other component classes. (A collection of different classes, where two or three select classes could be removed and the piece will function) Computer<>—keyboard,mouse
Composition
A strong form of aggregation relationship indicating a tight life cycle dependency between the composite parent class and its component parts. (a collection of different classes, where if you remove one part, the greater piece won’t function) Colllege<>—Faculty,Students
Generalization/Inheritance
An 'is a' relationship where child classes inherit common attributes, methods, and functionality defined in a parent class.
Interface
A collection of operations that a class carries out.
Realization
A class related to Interface. a class test implementing the Interface’s contract. Ex. Class—realization—(O
Dependency (Symbol)
A—O)—B with O being the interface and ) as the dependency. —-is the realization. B wants to use A.