Analysis Design System Notes

This set of flashcards covers key concepts, methodologies, and structures related to system design and development approaches, including SDLC and Agile methods.

The SDLC consists of several steps: 1) Identifying Problems, Opportunities, and Objectives - where the project scope is defined; 2) Determining User Information Requirements - gathering user needs; 3) Analyzing System Requirements - detailing technical and functional requirements; 4) Designing the Recommended System - creating design specifications; 5) Developing and Documenting Software - actual coding and documenting processes; 6) Testing and Maintaining the System - validating functionality and usability; 7) Implementing and Evaluating the System - deploying the system and assessing performance.

In developing an information system, we can use either System Development Life Cycle (SDLC), Agile Modelling, or Object Oriented Design. Draw the cycle and explain output of each step if the company chooses to use SDLC in developing the information system.

The Agile development process divides the project into small iterations or sprints, each lasting a few weeks. During each sprint, teams work collaboratively to develop a small piece of the application, allowing for constant reevaluation and feedback based on changing customer needs. Agile is suitable for this scenario because it provides flexibility and rapid adaptation to evolving requirements, which is critical for a startup catering to consumer demands.

A startup wants to develop an online shop application, but system needs often change according to customer demand. Therefore, the team chose to use the Agile method. Explain how the system development process is done with Agile in this case and why this method is suitable for use.

The SDLC is structured and proceeds in a linear sequence, making it less adaptable to changes. Agile allows for continuous iterations and flexibility in changing requirements. Object-Oriented Design (OOD) emphasizes modularity and reusability but may also align more with SDLC's structured approach unless combined with Agile principles. For a company facing rapid changes, Agile would be the most suitable approach due to its responsiveness to evolving business needs.

A company wants to develop a new information system to support its rapidly changing business needs. Explain how the development process would differ if the company uses the SDLC approach, the Agile approach, and Object-Oriented Design (OOD), and discuss which approach would be the most appropriate for this situation with reasons.

Maintainability is crucial as it determines how easily a system can accommodate updates and fixes over time. OOD supports maintainability through concepts like modularity, where systems are broken into manageable objects, making changes quicker and less risky by isolating alterations within specific classes or methods.

Why is maintainability an important factor in system design? Explain how Object-Oriented Design supports maintainability.

Feedback in organizational systems serves to compare current outputs against desired goals, highlighting areas for adjustment. This iterative feedback loop helps in planning and controlling operations. For instance, a sales team may receive feedback on monthly performance reports to adjust marketing strategies or sales tactics.

Discuss the role of feedback in organizational systems. How does feedback contribute to planning and control? Provide a clear example to illustrate your explanation.

The levels of management generally include: 1) Operational Control (Lower) - responsible for day-to-day operations and supervision; 2) Middle Management - focuses on tactical planning and coordinating activities between different departments; 3) Strategic Management (Upper) - responsible for long-term planning and alignment with organizational goals.

Mention the levels of management in a company? Explain the roles of each level of management.

An organization is considered a system because it transforms inputs (like resources and information) into outputs (products and services) through various processes. For example, a manufacturing company takes raw materials (inputs), processes them into finished products (outputs), and uses feedback from customers to improve production methods.

Explain why an organization is considered a system. In your answer, describe the roles of inputs, processes, outputs, and feedback using a simple example.

Context-level DFDs provide a high-level overview of a system and its interactions with external entities, whereas system-level DFDs detail internal processes and data flows. The ER model focuses on data structures and the relationships between entities. Both models are necessary as they complement each other; DFDs illustrate how data flows through the system, while the ER model details the underlying data architecture.

How do context-level and system-level Data Flow Diagrams (DFDs) differ from the Entity–Relationship (ER) model in representing business processes and data structures, and why are both models necessary in the design of an information system?

Creating a logical DFD first concentrates on understanding the functional aspects of the system without the constraints of technology. It ensures that business needs are accurately captured before considering physical implementations, leading to a system that better aligns with user requirements.

Explain why we should make a logical DFD before a physical DFD, and why focusing on what the system does first helps create a system that meets business needs.

Vertical balancing ensures that a child diagram's inputs and outputs align with those of the parent diagram, maintaining a consistent flow of information. This is crucial to ensure accuracy in data representation and process integrity across the DFDs.

Explain the concept of vertical balancing between a parent and child diagram. Why must the inputs and outputs be the same?

Partitioning in a physical DFD helps to organize and categorize processes for clarity and efficiency. Four reasons for grouping processes may include: 1) Timing - to indicate concurrent processes; 2) Security - to group sensitive information; 3) Complexity - to simplify understanding; 4) Functionality - to group related tasks that serve similar purposes.

Explain the role of partitioning in a physical DFD. Mention four reasons (such as timing or security) why processes are grouped together.

DFDs are easier to understand than written explanations because they visually represent the flow of data and processes, making relationships more apparent. They provide a clear conceptual framework that allows analysts to visualize and manipulate complex systems, facilitating deeper insights into the workings of a system during analysis.

Why is a DFD (visual diagram) easier to understand than a written explanation? Explain how DFDs give conceptual freedom during system analysis.

Output content and method are interrelated as the method chosen must be suitable for the type and volume of content being delivered. For example, a real-time dashboard displaying sales metrics requires a dynamic output method, like a web application, while a monthly report might be best suited for a printed format.

How are output content and the chosen output method related in an information system? Explain with a simple example.

Systems analysts should consider factors like user preferences, accessibility, the complexity of data, and the frequency of updates. For instance, a monthly performance report might be designed as a PDF document, chosen for its standard format that is easily shareable and viewable by users regardless of their operating system.

What factors should systems analysts consider when choosing an output method for users inside and outside the organization? Give one example of an output design and explain the method used and the reason for choosing it.

The alignment between output content and method is vital for effectiveness; if the method fails to suit the content type, users may find it difficult to interact or extract necessary information. An effective system ensures that both elements work harmoniously to enhance user experience and support decision-making.

How does the relationship between output content and output method influence the effectiveness of an information system in supporting user needs?

Digital output is more effective when immediacy and interactivity are required, such as for real-time data visualizations or interactive dashboards. Conversely, printed output may be preferred for formal documentation. For instance, a financial analyst might use software to generate an interactive dashboard for real-time stock performance, where complex data needs to be manipulated dynamically.

In what situations would digital output be more effective than printed output, and how do the type and complexity of output content influence the selection of the most appropriate output method? Provide a relevant example.