It243 Team Project Brief Description Students Will Conduct

It243 Team Projectbrief Description Students Will Conduct A Systems A

Students will conduct a systems analysis project by performing 3 phases of SDLC (planning, analysis and design) for a small (real or imaginary) organization. The actual project implementation is not required (i.e., no coding needed). The project involves applying classroom learning and participating in team work. Deliverables include a proposal, an oral presentation, and a final report, with specific deadlines in February and April.

Paper For Above instruction

The IT243 team project requires students to thoroughly analyze a small organization—either real or hypothetical—and execute the initial three phases of the System Development Life Cycle (SDLC): planning, analysis, and design. This project aims to cultivate practical understanding of systems analysis principles, refine team collaboration skills, and demonstrate the ability to translate theoretical knowledge into structured development processes. Although the project does not necessitate actual coding or implementation, students are expected to produce comprehensive documentation including diagrams and models that reflect each phase’s deliverables.

Introduction

The primary goal of this project is to simulate a real-world systems analysis scenario through structured phases. Students will select a topic or organization, define project objectives in a proposal, and develop detailed models depicting business processes, data, and system architecture. The project is a significant component of learning about SDLC phases, emphasizing planning, problem analysis, and system design without moving into coding or deployment stages. This approach encourages critical thinking, effective communication, and technical documentation skills essential for systems analysis professionals.

Project Phases and Requirements

Part 1: Planning Phase

• Adopt an SDLC development methodology, such as Waterfall, Agile, or Spiral, and justify the choice. This decision guides the structure and progression of the system development process.
• Develop a detailed work plan utilizing a Gantt chart that outlines tasks, milestones, deadlines, and responsibilities to ensure project organization and time management.

Part 2: Analysis Phase

• Determine and document the main business requirements of the organization, including core functionalities and user needs.
• Create Use Cases to illustrate interactions between users and the system, providing clarity on expected behaviors and system responses.
• Model Business Processes using Data Flow Diagrams (DFD) to visualize how data moves within the system, identify processes, data stores, and external entities.
• Model data structures through Entity-Relationship (ER) diagrams, illustrating data entities, attributes, and relationships essential for database design.

Part 3: Design Phase

• Select an appropriate architecture design considering factors like scalability, security, and user access; options may include client-server or layered architectures.
• Design system screens by creating layout sketches or wireframes for user interfaces, indicating navigation flow and user interactions without requiring HTML coding.
• Develop Class Design Diagrams to specify system classes, their attributes, methods, and relationships, aligning with object-oriented design principles.

Deliverables and Evaluation

The project results will be assessed based on the clarity, completeness, and professionalism of the documentation, including diagrams, models, and explanatory narratives. The key deliverables include:

1. Proposal document describing the project topic and methodology.
2. Detailed analysis models including use cases, data flow diagrams, and ER diagrams.
3. Design documentation comprising system architecture, user interface sketches, and class diagrams.
4. Final report synthesizing all phases and justifying design decisions.
5. Team oral presentation defending the project approach and findings.

Conclusion

This project offers an invaluable opportunity for students to practically apply SDLC concepts to a realistic scenario, fostering skills in systems analysis, modeling, and documentation. Effective teamwork, adherence to deadlines, and professionalism are critical to success. By focusing on planning, analysis, and design phases, students gain a comprehensive understanding of the foundational steps preceding software development, equipping them with essential competencies for future system development projects.

References

• Dennis, A., Wixom, B., & Roth, R. (2015). Systems Analysis and Design (6th ed.). Wiley.
• Larman, C. (2004). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Pearson.
• Shankar, R., & Krishnan, R. (2014). Software Engineering: A Practitioner's Approach. McGraw-Hill Education.
• Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach (8th ed.). McGraw-Hill Education.
• ISO/IEC 12207 - Systems and software engineering — Software life cycle processes. (2017). International Organization for Standardization.
• Yourdon, E. (2004). Structured Analysis and Design. Prentice Hall.
• Ambler, S. (2002). The Object primer: Agile model-driven development. Pragmatic Bookshelf.
• Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall.
• Gane, C. & Sarson, T. (1979). Structured Systems Analysis: Tools and Techniques. Yourdon Press.
• Bourgeois, D., & Kaddoura, H. (2018). Objectives and challenges of SDLC models. Journal of Systems and Software, 145, 128-139.