Scribd
Upload
Sign up
9 views1 page

System Analysis and Design Guidelines

This document outlines a 5-part project guideline for system analysis and design. Part 1 covers an introduction with background, objectives, scope, methodology, and schedule. Part 2 is on requirement gathering, including determining existing system problems and defining functional and non-functional needs. Part 3 is structuring system requirements through process modeling, logic modeling, alternative designs, and conceptual data modeling. Part 4 covers designing the new system database and user interface. Part 5 concludes with overall recommendations.

Uploaded by

zsam602
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
9 views1 page

System Analysis and Design Guidelines

This document outlines a 5-part project guideline for system analysis and design. Part 1 covers an introduction with background, objectives, scope, methodology, and schedule. Part 2 is on requirement gathering, including determining existing system problems and defining functional and non-functional needs. Part 3 is structuring system requirements through process modeling, logic modeling, alternative designs, and conceptual data modeling. Part 4 covers designing the new system database and user interface. Part 5 concludes with overall recommendations.

Uploaded by

zsam602
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.

System Analysis and Design

Project Guideline
o PART ONE: Introduction
 Overview and Background
 Problem/Opportunity Statement
 Objectives of the Project
 Significance of the Project
 Scope of the Proposed System
 Methodology
 Feasibility Analysis of the Proposed IT Solutions
 Schedule (Identifying the Tasks and Time Frame)
 Communication Plan
o PART TWO: Requirement Gathering
 Determining system requirements
 Detail overview of the existing system using Requirement
gathering techniques
 Problems encountered by the existing system
 Requirement definition
 Functional requirements
 Non functional requirements
o PART THREE: Structuring System Requirements
 process modeling
 Different level DFDs
 Data Dictionary
 logic modeling of the new system
 structured English or Decision tree or Decision table
 generating and selecting the best alternative design strategy
 Conceptual data modeling of the new system
 Identifying Entity Types and attributes
 identifying, attribute, relationship degrees and names/types
among entities
 ER modeling
o PART FOUR: Design of the New System
 Database design
 Logical database design and Physical database design
 User Interface design
 Forms and reports design
 Dialogue Design
o PART FIVE: Conclusion and Recommendation
 Conclusion & Recommendation

Note:
Prototype of the System Should be attached to the document with CD.

You might also like