Software Engineering

		      Software Engineering Final
		      ==========================

Chapters  1-10
          12-15
          21-27


			      GUI DESIGN
			      ==========

These are common issues in GUI Design
       System response time
       Help facilities
       Error Handling
       Command labeling

This design technique which is focused on the GUI is also an
            evolutionary process model
     Prototyping

This is the term which describes a scenario where the user understands
        how to operate a user interface based on experience with
        similar interface conventions in the past.
     Familiarity

This establishes the first impression of a application or web site.
     The User Interface
     Alternative answer: how long it takes to load (via JK)

These are the Golden Rules of user interface design.
      Be Consistent.
      Reduce the user's memory load
      Place the user in control


                               CHANGES
                               =======

This is a process that manages the evolution of all software
        development artifacts with the goal of ensuring product
        integrity.
     [Software] Configuration Management (SCM)

This word is used to describe any work product that results from the
          software engineering process.
     Artifact

These are advantages provided be a formal SCM repository.
      Central authority of the current state of the game (data integrity)
      Information sharing
      Tool integration
      Data integration
      Methodology enforcement
      Document standardization

This concept identifies a formal, documented point at which all
             software artifacts are inventoried and compared against
             over time.
     Baseline

This is a mechanism for evaluating and approving (or disapproving)
        proposed changes to configuration items and for ensuring
        implementation of approved changes.
     Configuration Control Authority (buzzwords, man)


                               TESTING
                               =======

This is the most expensive phase of the software life cycle in which
        to correct bugs.
     [After] Deployment

This, according to the author of our textbook, is the additional cost
                associated with uncovering software errors after
                deployment
      Between 40 and 1000 times the cost of uncovering the error
                earlier in the software's development

These are considered External Software Failure costs
      Lost credibility
      Complaint resolution
      Product return and replacement
      Help line support

This type of testing involves the testing of individual modules and
          methods and exercises internal processing logic and data
          structures
     Unit testing

These two items are commonly used to simulate interaction with other
          software components by those performing unit testing
      Stubs
      Drivers

                          VARIOUS AND SUNDRY
                          ==================

This estimation technique considers the number of inputs, outputs,
                user inquiries, files, and external interfaces.
     Function Point Analysis

This type of modeling defines objects, attributes, and relationships
     Class-Based Modeling

This is the structure (or organization) of program components
        (modules), the manner in which the components interact, and
        the structure of data that are used by the components
     Software Architecture

This technique, which is conducted with other development team
                members, is used to discover technical errors and
                errors of understanding early in the software
                engineering process
     Peer review

This is the equation used to determine the number of communication
        paths between team members, where N is the number of people on
        the team
     \frac{n*(n-1)}{2}


                              DOCUMENTS
                              =========

This document is used to map requirements to some other item, such as
              aspects of the software
     Traceability matrix

This document is used to plan the approach and resources for a
              software project
     Software Development Plan (SDP)

This document is used to formally state the entire set of functions
              and features that the software system is expected to
              have
     Software Requirements Specification (SRS)

This document is used to state the set of procedures that will be used
              to assess software reliability and adherence to
              requirements
     Software Test Plan (STP)
     Alternative Answer: Software Test Procedures

This document is used to describe in detail the design details used in
              the development of the software system
     Software Design Document (SDD)


                            ANYTHING GOES
                            =============

This is the cause for recurring increases in software failure rates
        late in the software's life cycle
     Software upgrades and updates
     Alternative Answer: Changes in requirements

These are older, well-established programs that (generally) are still
          used today because they provide some benefit to an
          organization
      Legacy software

This type of data analysis attribute describes whether a data
          relationship is one-to-one, one-to many, or many-to-many
     Cardinality

This practice defines five levels of process maturity
     Capability Maturity Model Integration (CMMI)

This process model attempts to accept and accommodate change better
             than conventional methods and emphasizes rapid delivery
             of operational software
     Agile [Development]


                          LIFE CYCLE MODELS
                          =================

This process model, which is a high-speed adaptation of Waterfall
             model, utilizes multiple software teams which work in
             parallel on different system functions.
     Rapid Application Development (RAD)

This is the model in which models of the user interface are developed
        and discussed with customers and users in order to define
        features, functions, and user interface conventions
     Prototyping

This is an evolutionary process model which combines the iterative
        nature of prototyping with the controlled and systematic
        aspects of the Waterfall process model
     Spiral Model

This evolutionary process model is organized into a set of framework
                  activities and each framework activity is then
                  organized into a set of actions and tasks.  Each
                  activity then goes through phases independently, not
                  together.
     Concurrent Development Model

This process model involves a set of activities that leads to formal
             mathematical specification (models) of computer software.
     Formal Methods Model

                      SOFTWARE PROCESS FRAMEWORK
                      ==========================

This activity includes analysis and design tasks.
     Modeling

This activity involves assessing the project scope, producing
              estimates, and considering all applicable risks.
     Planning

This activity encompasses coding and testing tasks that lead to
              operational software.
     Construction

This activity involves the installation and initial use of the
              software product.

     Deployment

This activity involves discussions and meetings with the customer to
              identify the functions of the software.
     Communication

                           MORE ON TESTING
                           ===============

This testing activity is performed after integration testing, and is
             conducted in the real-world computing environment that
             the software will be used in.
     System testing
     Alternative answer: In-house testing

This testing technique results in test cases that are intended to
             execute every statement in the program at least once.
     Basis Path testing

This type of test is based on knowledge of internal workings of
          software and is associated with unit testing.
     White-box testing

This is a formal, structured set of test instructions which is
        (ideally) developed in advance of code.
     Test Cases [/Procedures]

This testing activity ensures that the software that has been built is
             traceable to the customer requirements.  (It tests that
             we are building the right product.)
     Validation

                        REQUIREMENTS CONCEPTS
                        =====================

These are three reasons which explain why gathering requirements is a
          difficult process.
      1.  Problems of Scope
      2.  Problems of Understanding
      3.  Problems of Volatility

This process can be enabled through the creation of user scenarios and
             describe how the various users (roles) will interact with
             the system.
     Elaboration

This is the process of reconciling conflict.
     Negotiation

This is the best way to communicate with customers when collecting
     	requirements.
     Face-to-face

These are areas to consider when defining requirements.
      1.  Functional
      2.  Mode or state requirements
      3.  Performance
      4.  Re-use
      5.  External & Internal Interfaces
      6.  Safety
      7.  Security
      8.  Environmental
      	  -  Physical
	  -  Developmental
	  -  Cultural
      9.  Hardware Resources
     10.  System Quality
     11.  Documentation
     12.  Personnel
     13.  Training
     14.  Schedule
     15.  Testing
     16.  Installation
     17.  Maintenance
     18.  Packaging

			    RISKY BUSINESS
			    ==============

These are the three categories of risk for software projects.
      1.  Project Risk
      2.  Technical Risk
      3.  Business Risk

These are the five steps in the Risk process.
      1.  Risk Identification
      2.  Risk Analysis
      3.  Ranking Risks
      4.  The Risk Plan
      5.  Monitor Risks

These two risk attributes are considered when assessing each risk.
      1.  Consequence
      2.  Likelihood

This is a Software Engineering plan which identifies evaluations to be
     	performed, applicable standards, procedures, metric
     	collection, and reporting.
     Software Quality Assurance (SQA) plan

Performing this step defines a risk strategy as proactive, as opposed
	   	to reactive.
           Risk Mitigation Planning

			   ANYTHING GOES II
			   ================
In Agile development, this is the fixed period of time during which a
   	 given set of work tasks will be worked.
   Sprint

These are characteristics of a good requirement.
      1.  Unambiguous
      2.  Verifiable
      3.  Complete
      4.  Consistent
      5.  Modifiable
      6.  Traceable
      7.  Usable

This is the process of managing change.
     Configuration/Change Management

This activity accounts for the largest percentage of technical effort
     	      in the software process.
     Software Testing

This is a metric or combination of metrics that provide insight into
     	the software process, project, or product.
     Indicator

END OF JEOPARDY GAME