System Analysis and Design
Semester III · BCA 204 · 3 credits
0 / 5
chapters done
-
The syllabus asks for
- The systems development environment
- Modern approaches to systems analysis and design
- The systems development life cycle (SDLC)
- CASE tools
- Service-oriented architecture
- Agile methodologies and Extreme Programming
- Object-oriented analysis and design
- The origins of software and system acquisition
- Managing the information systems project
- The life cycle as a picture, and agile practice in the field
- Eight reasons why a systematic life cycle matters
Key points
- Information systems come in several types and are built through an SDLC under a chosen model; each model trades predictability for flexibility.
- CASE tools, SOA and OOAD/UML are supporting technologies; agile methods and XP emphasise short iterations.
- Software may be built, bought, outsourced or reused; the project manager schedules with Gantt charts and the critical path method.
-
The syllabus asks for
- Identifying and selecting systems development projects
- Corporate and information systems planning
- Initiating and planning a project
- Assessing project feasibility
- Building and reviewing the baseline project plan
- Seeing the payback, and planning the schedule
- Eight reasons to do a feasibility study first
Key points
- Projects are identified from many sources and selected with explicit criteria aligned to corporate strategy.
- Initiation sets up the team, charter, scope and management procedures.
- Feasibility tests, especially cost-benefit measures (NPV, ROI, payback), decide whether to proceed.
- The baseline project plan is reviewed by walkthrough and becomes the standard for later phases.
-
The syllabus asks for
- System requirements and how to determine them
- Process modelling: data flow diagrams
- System data requirements: conceptual data modelling
- Three models drawn out: context, level-0 and entity-relationship
- Eight benefits of modelling before building
Key points
- Requirements are gathered by interviews, questionnaires, observation, documents, JAD, prototyping and, in agile projects, user stories; BPR rethinks processes.
- DFDs model processes in levels with strict rules and balancing; decision tables, structured English and trees model complex logic.
- Conceptual data models use E-R notation with supertypes, subtypes, business rules and reusable patterns.
-
The syllabus asks for
- Designing databases
- Physical file and database design
- Designing forms and reports
- Designing interfaces and dialogues
- Normalisation and screen design, drawn out
- Eight rules for good forms, reports and interfaces
Key points
- Logical design normalises user views, converts E-R diagrams to relations and merges them.
- Physical design chooses field formats, tables, file organisations and indexes, trading storage and update cost for speed.
- Forms and reports follow consistent, logical, accurate-and-usable guidelines and are assessed with usability testing.
- Interface and dialogue design uses the interaction method suited to the user, consistent GUI controls and clear feedback and error messages.
-
The syllabus asks for
- System implementation
- System maintenance
- Testing levels, installation strategies and maintenance types, in pictures
- Eight reasons why testing and maintenance planning pay off
Key points
- Implementation covers coding, multi-level testing, installation, documentation, training and support, and must manage organisational change.
- Installation strategies trade risk against cost; documentation serves maintainers and users.
- Maintenance (corrective, adaptive, perfective, preventive) is the longest and costliest phase, governed by change control and configuration management.
No chapter matches. Try another word.
The paper
TU assessment: 60% final examination set by the university, 40% internal (assignments, lab work, attendance). Confirm the split in your college's notice.
Where the hours go
Teaching hours are the board's guide to how much of the paper each part carries.
- Unit 3 · Analysis13 h
- Unit 4 · Design12 h
- Unit 1 · System Development Fundamentals9 h
- Unit 2 · Planning7 h
- Unit 5 · Implementation and Maintenance4 h