Cross Life-Cycle Activities

Cross Life-Cycle Activities is any activity that overlaps many or all phases of the systems development process.

• Fact-finding: the formal process of using research, interviews, meetings, questionnaires, sampling, and other techniques to collect information about system problems, requirements, and preferences.
•  Documentation: recording facts and specifications for systems for current and future reference.
• Presentation: communicating findings, recommendations, and documentation for review by interested users and managers.
•  Repository: database and/or file directory where system developers store all documentation, knowledge, and artifacts for information systems or project(s).
•  Feasibility analysis: Process and project management Cycle Activity

Sequential Development

Sequential models such as Waterfall or V-Model rely on intensive periods of collecting and refining requirements for a product before design and development activity can take place. Products developed using these models are intended to be complete when released to customers. Central to the approach is an assumption that by adhering to the requirements captured at the outset, the product will fulfill the wishes of those customers:

Iterative Development

This is in contrast with iterative ways of working, with an emphasis on delivering less complex products, often to test customer response before making adjustments. The techniques encourage regular feedback from customers, and rapid response to that feedback; refining ideas and revisiting design and development activities with the intention of delivering products that better reflect what customers want:

Automated Tools and Technology

Computer-Aided Software Engineering refers to automated system tools used by systems analysts to develop an information system.

USE of case

• The case can support most of the system development activities.
• The case helps provide an engineering-type discipline to software
  development and automation of the entire software life cycle
  process.

Objectives to case

• improve the quality of the systems developed.
• increase the speed with which systems are designed and developed.
• ease and improve the testing process through the use of automated checking.
• improve the integration of development activities via common methodologies.
• improve the quality and completeness of documentation.
• help standardize the development process.
• improve the management of the project.
• simplify program maintenance.
• promote the reusability of modules and documentation.
• improve software portability across environments.

Categories of case products

Reverse engineering

automated tools that read program code as input and create graphically and textual representations of program design-level information such as program control structures, logical flow, and data flow.

Reengineering

automated tools that read program source code as input, perform an analysis of the program's data and logic, and then automatically or,
interactively with a systems analyst, alter an existing system in an effort to improve its quality or performance.

Components of case

The upper case-- case tools designed to support the information planning and the project identification and selection, project initiation and planning, analysis and design phases of the SDLC
The lower case--case tools are designed to support the implementation and maintenance phases of the SLDC.
Cross life cycle case--case tools designed to support activities that occur across multiple phases of the SLDC