Cs360 Test1
Unified modeling language
"A family of modeling techniques consisting of more than twenty diagram types that can be used to represent a model for a system from multiple perspectives"
Design thinking
"A process model for designing product and service innovations."
Feasability analysis
"A process to determine whether or not it is reasonable to expect that a project can be completed successfully."
Design
"A software requirement that describes how a feature will be designed to work, including such issues as specifying logic and rules, data, and the user interface."
Feature
"A software requirement that describes what a software system should be able to do, expressed without regard to how that capability will be designed or work."
"Plan-driven approach"
"A traditional approach to creating products in which key activities are executed one after the other in a linear fashion. "Traditional SDLC" and "waterfall" are examples"
User Story
"A way of describing a feature that answers three key questions: Who will use the feature, what the feature will do, and why the feature adds value."
Prototyping
"A widely used methodology in product design in which models with limited capabilities are used as a mechanism for communication between designers and clients."
"Commercial off-the-shelf (COTS) software"
"Software written by a software vendor and intended to be sold or rented to other client organizations."
Acceptance criteria
Criteria that have to be fulfilled for an implementation of a user story to be acceptable. These serve as constraints that limit acceptable implementation options.
Greenfield development
Development of an entirely new system
Brownfield development
Enhancement of an exiting system
business analysis
discovering and structuring the ways in which an organization can transform the way it operates in order to more effectively achieve its goals
Hybrid Approach
"Approach to developing software that combines the BRUF approach of plan-driven with the iterative construction approach of agile."
Business Model
"Articulation of the logic of the business and the value proposition that the business offers to its customers"b
Emergent Requirements
"Capturing only key feature requirements up front, and then developing detailed designs as they emerge during the course of software construction. Often associated with agile approaches"
"Big requirements up front (BRUF)"
"Creating detailed software requirements early in the project, generally prior to starting software construction or configuration."
Operational Decision
"Decisions related to everyday operations of an organization"
Tactical Decision
"Determining how an organization will achieve its strategic goals."
Strategic decision
"Long-term, rare, and important decisions about which high-level activities the organization will continue to be engaged in and which ones it will abandon."
Cybersecurity
"Measures taken to protect a computer or computer systems against unauthorized access or attack"
UML activity diagram
"One of behavior diagrams in UML that can be used to describe the activities in an organizational process and the control and object flows between the activities. One of the most widely used UML diagram types."
"Transaction processing"
"One of two broad categories of business application systems, focused on creating, processing, and finalizing individual data transactions, such as orders, shipments, insurance claims, and so forth"
Systems analysis and design (SA&D)
"Organizational activities to determine how IT-based solutions can be applied within an organization to help it achieve its goals."
"Business analysis"
"Process of understanding how a business currently operates and determining how that process should change in the future to support the business's goals via a software project."
Agile Approach
"Relatively recent general approach to developing software, emphasizing maintaining a high degree of flexibility and responsiveness to changing requirements and priorities"
Change Management
"Series of tasks that must be completed for the business organization to be able to successfully deploy a new or enhanced software system."
Application software
"Software designed to accomplish business or personal goals (e.g., processing transactions or turning those transactions into management information).
System Software
"Software that provides functions to develop or run application software, such as programming languages, operating systems, and database management systems"
Requirements
"The combination of features and corresponding functional design that, together, define a product" "• Requirements: A product (for example, a vehicle) must be defined by a set of requirements, including features (what the product must do) and functional designs (how the product must deliver the features).
System Analysis
"The portion of the systems analysis and design process focused on determining a system's features."
"Systems design"
"The portion of the systems analysis and design process focused on determining the designs needed to deliver a system's features"
"Initial visioning"
"The process of determining at a high level the business problem or opportunity that a software project should address, the key system capabilities to be created, and the business benefits expected to be achieved."
Future State
"The way a business organization will operate in an environment in which the problem or opportunity identified is addressed by the new or improved software"
"Current state"
"The way an organization currently operates, including problems or opportunities for improvement that may be addressed using new or improved software."
Skills that only humans have that are needed for creating software
- Creativity - Large-frame pattern recognition - Asking interesting questions - Complex communication - Common sense
Mock-up
A highly abstract model of an application or a web page that defines key structural elements without details
Wireframe
A highly abstract model of an application or a web page that defines key structural elements without details
User interface prototype
A model of an application with a limited implementation of key functionality
User interface model
A model of an information system user interface that allows a user to explore the systems capabilities in an easily understandable way
Feasibility Analysis
A process for determining from multiple perspectives whether or not a project will be able to acheive its goals
Swim lane
A section of an activity diagram reserved for activities performed by a specific actor
Activity
A set of actions that an individual or a group tales that contributes to the outcome of a process
Decision node
A symbol in an activity diagram illustrating multiple possible outcomes selected based on well-defined criteria
Epic
A user story that summarizes a broad range of user needs
Persona
An organizational role in which an individual uses an information system to achieve a goal
Control flow
Movement of control within an activity diagram from one activity to another
Fork/join
Symbols in an activity diagram signifying the beginning and the end of a set of parallel activities
Intelligent modeling
The principle of creating requirements artifacts only when they ad value in a given project context at a particular stage of the process
Automation boundary
Virtual seperation between computing based system activities and human activities in the context of an org system
Customer Value
• Customer value: If either requirements specifications or construction activities are performed poorly, then the customer will judge the product to be a failure, but for different reasons. Plainly stated, poor construction results in the right product with bad quality. But poor requirements result in the wrong product altogether—arguably a more fundamental problem."
Implementation
• Implementation: Further, requirements then must be transformed into an actual product. In the car and truck examples, we would typically think of fabricating and assembling parts through a process of construction. Note that later we will describe a systems alternative to construction called configuration.
