CC326 Midterm Exam Reviewer

• It refers to a set of computer science activities dedicated to the process of creating, designing, deploying, and supporting software.

  Software Development
• It is the process of designing, building, and implementing software applications.

  Application Development
• It is the process of planning, designing, creating, testing, and deploying a software application to perform various business operations.

  Application Development
• A branch of computer science that deals with the design, implementation, and maintenance of complex computer programs.

  Software Engineering
• It is a systematic approach to the analysis, design, implementation and maintenance of software.

  Software Engineering
• Types of Software

  • Bespoke
  • Generic
• A type of software that is mass produced with the intention that it will be used by a wide variety of different users in a range of different situations.

  Generic Software
• A type of software that is created for a specific purpose which will be used in a known environment.

  Bespoke Software
• Categories of Software

  • System
  • Application
  • Engineering/Software
  • Embedded
  • Product-line
  • Web Applications
  • Artificial Intelligence
• A collection of programs written to service other program.

  System Software
• Consists of standalone programs that solve a specific business need.

  Application Software
• Formerly characterized by “number crunching” algorithms.

  Engineering/Scientific Software
• Resides within a product or system.

  Embedded Software
• Address to mass consumer markets.

  Product-line Software
• Set of linked hypertext files.

  Web Applications
• Application within this area includes robotics, expert systems, pattern recognition and game playing.

  Artificial Intelligence Software
• Kind of Prototypes

  • Patched-Up Prototype
  • Nonoperational Prototype
  • First -of-a-Series Prototype
  • Selected Feature Prototype
• constructing a system that works by is patched up or patched together. referred to as breadboarding: creating a patched-together, working model

  Patched-Up Prototype
• model of an information system might be produced when the coding required by the application is too extensive to prototype

  Nonoperational Prototype
• involves creating a first full scale model of a system. useful when many installations of the same information system are planned.

  First-of-a-Series Prototype
• concerns building an operational model that includes some. features that the final system will have

  Selected Feature Prototype
• Developing a Prototype

  • Work in manageable modules
  • Building the Prototype Rapidly
  • Modifying the Prototype
  • Stressing the User Interface
• Prototype process

  • Identify basic requirements
  • Develop initial prototype
  • Revise and enhance the prototype
• It is an object-oriented approach to systems development that includes a method of development as well as software tools.

  Rapid Application Development (RAD)
• Refers to a type of software development methodology that uses minimal planning in favor of rapid prototyping.

  Rapid Application Development (RAD)
• Phases of RAD

  • Requirement Planning
  • RAD Design Workshop
  • Implementation phase
• collection of innovative, user-centered approaches to systems development.

  Agile Modeling
• Four Values of Agile Modeling

  • Communication
  • Simplicity
  • Feedback
  • Courage
• Four Basic Activities of Agile Development

  • Coding
  • Testing
  • Listening
  • Designing
• Designing

  • Time
  • Cost
  • Quality
  • Scope
• Waterfall approach was established in 1970 by _________.

  Winston W. Royce
• It is ideal for projects like software development, where the end result is

  clearly established before starting, and is best suited for projects that require a lot of predictability.

  Waterfall Methodology
• Phases of Waterfall Methodology

  • Requirements
  • Design
  • Implementation
  • Verification
  • Maintenance
• A system development lifecycle (SDLC) method used for risk management that combines the iterative development process

  Spiral Model
• Also referred to as the Verification and Validation Model. In this, each

  phase of SDLC must complete before the next phase starts. It follows a sequential design process

  V-Model
• 2 Phases of V Model

  • Verification
  • validation
• Various phases of Verification Phase

  • Business requirement analysis
  • System Design
  • Architecture Design
  • Module Design
  • Coding Phase
• Various phases of the Validation Phase

  • Unit Testing
  • Integration Testing
  • System Testing
  • Acceptance Testing
• It is an objective of each and every activity where we want to discover

  things that belong to the project.

  Planning
• This includes the manual of operation of the system, the possible

  solutions to the possible problems of the user, the budgetary allocation, time schedule and other possible discussions related to the development of the system.

  Documentation