This paper presents an individual learning reflection on system analysis and design (SA&D) using the Broadway Entertainment Company (BEC) case study as a practical reference. It explores the core concepts of the system development life cycle (SDLC), including context diagrams, data flow diagrams (DFDs), and data dictionaries. The paper examines team dynamics, outlining the attributes of effective team members such as integrity, creativity, and open communication. It also discusses the lessons students draw from the BEC case, the roles they envision for themselves in real projects, and the analytical and technical skills they must develop to become proficient system analysts and designers.
System analysis and design is the process of planning, analyzing, designing, and implementing information systems to meet business needs. As defined in the literature, "systems analysis is a process of collecting factual data, understanding the processes involved, identifying problems, and recommending feasible suggestions for improving the system functioning" (Open Schooling, 2010, p. 5). System design, on the other hand, is the process of converting business requirements into a physical system design. To design a system, a designer makes use of tools such as flowcharts, Data Flow Diagrams (DFDs), data dictionaries, and structured English to build functional information systems.
The Broadway Entertainment Company (BEC) case study serves as a prototype of the system development life cycle (SDLC), in which a group gathers relevant data to analyze and design an information system. Although the BEC case does not reflect the complete SDLC, it nonetheless provides a valuable learning experience for developing skills in system analysis and design.
There are several individual learning experiences that emerge from studying system analysis and design. One key takeaway is an understanding that SA&D is part of the broader system development life cycle (SDLC), which involves planning, analyzing, designing, and implementing functional information systems. Students learn that to become a system analyst, a person must collect relevant data from users. This data collection is used to analyze the objectives of the system and its proposed benefits. This stage is particularly important for identifying problems in the development of information systems and determining methods to overcome them.
Additionally, students learn that designing a system involves distinct stages. First, a context diagram must be created, followed by a Level 0 DFD and Level 1 diagrams. The purpose of a Data Flow Diagram is to provide a blueprint of the components and inter-relationships within the system design.
The BEC case study enhances the learning experience because it allows students to understand that the context diagram is the first step in designing a system. The context diagram in the BEC case partially satisfied user requirements. It illustrated how customers interact with the system to request movies, and how the system interacts with the entertainment tracker to determine whether a customer is eligible to rent a movie based on a rental agreement. A review of the context diagram reveals, however, that it is not sufficiently detailed — specifically, the role of the store manager needs to be incorporated (Broadway Entertainment Company Inc., n.d.).
Furthermore, the case study does not present a Level 0 or Level 1 diagram in complete form. Although team members proposed methods for designing these diagrams, it became clear that automated design tools are essential for eliminating syntax errors. The reflection from the BEC case study ultimately underscores that a cohesive and capable team is critical to designing effective functional information systems.
Experience from this learning process has revealed that effective team members can significantly contribute to the success of a project. For a project to achieve its goals, team members ought to possess certain attributes and characteristics. The key attributes of a valuable team member include the following:
Result-driven: A team member should be result-driven, working diligently with the team's objectives in mind, allowing those shared objectives to take precedence over personal goals.
Integrity: Team members should uphold high personal standards and consistently act in the best interest of the team.
"Key traits of valuable project team members"
"Collaboration and decision-making insights gained"
"Student as analyst; skills to develop"
Espindola, D. (2009). The 7 traits of highly effective teams. Self-Improvement Magazine.
Open Schooling. (2010). Introduction to system analysis and design. National Institute of Open Schooling.
You’re 46% through this paper. Sign up to read the remaining 3 sections.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.