Parallel Development Methodology Quiz

Systems Analysis and Design

• Chapter 1 introduces the systems development life cycle (SDLC), a four-phase model that consists of planning, analysis, design, and implementation. This model is commonly utilized in various domains of information systems development to ensure a structured and systematic approach to delivering technology solutions that meet organizational needs effectively.
• The chapter not only emphasizes the SDLC but also describes the evolution of systems development methodologies. It elaborates on how these methodologies have adapted over time to meet the changing demands of technology and business environments. Additionally, the chapter discusses the diverse roles and skills involved in systems analysis, highlighting the importance of collaborative efforts in successful projects.
• Moreover, the chapter provides an overview of the characteristics of object-oriented systems, explaining the fundamentals of object-oriented systems analysis and design (OOSAD). This includes a detailed discussion of the Unified Process, a prominent development framework, and its extensions while also introducing the Unified Modeling Language (UML), which serves as a standardized visual language for modeling software systems.
• The objectives of this chapter include a comprehensive understanding of the SDLC and its individual phases, insight into the evolution of development methodologies, identification of various roles and skills of systems analysts, a solid grasp of object-oriented systems analysis and design (OOSAD), and familiarity with the Unified Process and Modeling Language, all of which are critical in navigating the complexities of system development.

Chapter Outline

• Introduction: This section discusses the critical importance of systems analysis in comprehensively understanding business needs and designing effective and efficient information systems. It clarifies that the SDLC should not be viewed as a single "silver bullet" solution; instead, it is a collection of concepts and methodologies that aim to enhance the probability of success in systems development endeavors through a structured approach.
• The Systems Development Life Cycle (SDLC): This part provides a detailed description of the four fundamental phases within the SDLC: planning, analysis, design, and implementation. Each phase plays a crucial role in ensuring that the system meets business requirements and stakeholder expectations.
• Planning: This phase serves as the fundamental process for understanding the necessity of the system and identifying its business value. It encompasses a comprehensive feasibility analysis that assesses various aspects including technical viability, economic feasibility, and organizational compatibility. This phase requires a system request, which is a formal document detailing the need for the system that is presented to an approval committee for evaluation and approval.
• Analysis: In this phase, a thorough examination is conducted to ascertain who will be using the system, the intended functions it must perform, and the context in which it will be utilized. Research into the current system is carried out alongside the development of a new system concept that incorporates diverse business analysis models. The outcome of this phase is a well-crafted system proposal that is presented to project stakeholders, encompassing all necessary insights and recommendations.
• Design: This stage involves detailing how the system will function, addressing various components such as hardware, software, user interfaces, forms, reports, and programs. It builds upon the foundational system concept that emerged during the analysis phase. The design phase is structured into four main steps: strategic planning, architectural design, database design, and program design. Its primary aim is to specify distinct operational parameters of the system to ensure that all functional requirements are met effectively.
• Implementation: This crucial phase deals with the actual construction or acquisition of the system. It includes steps that encompass system construction – which involves building and testing of the system – as well as installation, which signifies the transition from the old system to the new one. Additionally, the phase entails planning for implementation support, which includes comprehensive training for users to facilitate a smooth transition and maximize adoption of the new system.
• Systems Development Methodologies: This section addresses the various methodologies available for systems development which include Structured Design, Rapid Application Development (RAD), and Agile Development.
  • Structured Design: This approach embodies a formalized step-by-step methodology used in systems development, with Waterfall development being a widely recognized example. This method is characterized by its linear, sequential phases, each neatly delineated for clarity and emphasis on thorough completion before moving to the next.
  • Rapid Application Development (RAD): RAD aims to accelerate the development process by employing innovative techniques such as Computer-Aided Software Engineering (CASE) tools and other computer-aided design tools. The focus lies in enhancing both the speed and quality of systems development through increased user involvement and iterative prototyping, optimizing the development timeline while ensuring stakeholder satisfaction.
  • Agile Development: This methodology prioritizes iterative development, advocating for frequent user feedback and a highly flexible approach throughout the development lifecycle. Methodologies such as Extreme Programming (XP) and Scrum exemplify Agile practices. Unlike traditional methodologies that often prioritize comprehensive documentation, Agile development emphasizes quick adjustments and adaptability, reflecting a profound commitment to effectively meet the evolving needs of customers.
• Typical Systems Analyst Roles and Skills: This section outlines the various roles and skills that are essential to a systems analysis project team. Key positions identified include business analyst, who focuses on articulating and addressing business issues; systems analyst, who concentrates on the information technology aspects; infrastructure analyst, who focuses on the technical infrastructure of a system; change management analyst, who handles the user impact resulting from system changes; and project manager, who oversees and coordinates the entire project team and its various activities.

Object-Oriented Systems Analysis and Design (OOSAD)

• Classes and objects: In object-oriented programming, classes serve as blueprints or general templates from which objects are created. Objects, on the other hand, are specific instances of classes that encapsulate both data and functionalities defined by their class, making them integral components of object-oriented systems.
• Methods and messages: Methods play a crucial role in implementing an object's behavior by defining the actions that can be performed on an object. A message is what triggers a method within an object, facilitating communication between various components of the system and ensuring that operations are executed as intended.
• Encapsulation and Information Hiding: Encapsulation involves bundling data and the associated processes within objects, effectively concealing internal details from the outside world. This strategic isolation enhances security and maintainability by adhering to the principle of information hiding, which allows developers to modify the internal structure of an object without creating a ripple effect on other components of the system.
• Inheritance: This principle facilitates the organization of objects into hierarchies, where subclasses inherit properties and methods from their parent classes (superclasses). Such a structure reduces redundant code, promotes code reuse, and simplifies maintenance since changes made in a superclass automatically propagate to its subclasses.
• Polymorphism and Dynamic Binding: Polymorphism allows messages (such as method calls) to trigger different behaviors in different object types, thus providing a high degree of flexibility and generalization in programming. This flexibility is enhanced through dynamic binding, where decisions regarding method execution are deferred until runtime, allowing the system to adapt to varying contexts without rigid constraints.

The Unified Process

• This methodology offers a structured framework for object-oriented analysis and design (OOSAD), comprising several distinct phases: Inception, Elaboration, Construction, and Transition, with the optional Production phase dedicated to ongoing operations.
• Every phase within the Unified Process contains specific engineering and supporting workflows, contributing to a sequence of deliverables and work activities that guides the overall development effort. This ensures that all critical aspects are covered in an organized manner.
  • Inception: This initial phase focuses on business modeling and gathering requirements, ensuring that the needs of stakeholders are identified and documented comprehensively to guide subsequent phases.
  • Elaboration: This phase emphasizes the detailed analysis and design of the system, where insights gained from the inception phase are translated into a more concrete framework for development.
  • Construction: During this phase, the primary focus shifts towards the actual implementation of the system along with rigorous testing to ensure that it meets predefined requirements and standards.
  • Transition: In this critical phase, there is a focus on the deployment of the system and ensuring user acceptance. Careful planning and execution are necessary to facilitate a smooth transition from development to production.
  • Production: This optional phase centers on the ongoing support and maintenance of the system once it is released to users. This includes addressing issues that arise during operation and considering upgrades or modifications.

The Unified Modeling Language (UML)

• UML provides a standardized set of diagramming techniques that serve as visual tools for depicting object-oriented systems. These diagrams bridge understanding gaps among stakeholders, enhancing communication and clarity throughout the development process.
• Structure diagrams are used to illustrate a system's static data organization and relationships among its components, which include elements like class diagrams, object diagrams, package diagrams, deployment diagrams, component diagrams, and composite structure diagrams.
• Behavior diagrams, on the other hand, visually represent a system's dynamic behavior. They encompass use case diagrams, sequence diagrams, communication diagrams, interaction overview diagrams, timing diagrams, state machine diagrams, and protocol state machine diagrams, allowing stakeholders to grasp how a system responds to different inputs and situations.