Business Systems Analysis lecture notes 2012
For the Business Systems Analysis class, students please refer to the following notes:
You need to study the subject manual.
Major topics are as follows:
Exam is 1 hour 30 mins., closed book.
Class exercise on rich picture building:
Also refer to the folder notes on rich picture building: https://www.facebook.com/media/set/?set=a.10150261845082090.378645.713727089&type=3
ES:
Electronic Commerce textbook mentioned in last workshop: http://www.pearsonhighered.com/educator/product/Electronic-Commerce-2010/9780136100362.page
References
- Systems Development Life Cycle
- Project management for systems development
- CASE tools
- Dynamic Systems Development Method
- Soft Systems Methodology for systems development
- Considerations on purchase of software applications for enterprises
- Quality Assurance for software development
- UML notations with special reference to Use Cases and Activity Diagrams
- Some briefing on Data Flow Diagrams, and a few minispecifications, e.g. Structured English, Decision Table, Decision Tree
- Software Testing
- A manufacturer on toys located in PRC
- Products sold to South Eas Asia
- 3 suppliers nearby the factory
- Main theme: problem with the inventory control system
Also refer to the folder notes on rich picture building: https://www.facebook.com/media/set/?set=a.10150261845082090.378645.713727089&type=3
- SDLC: http://en.wikipedia.org/wiki/Systems_development_life-cycle
- Agile software development: http://en.wikipedia.org/wiki/Agile_software_development
- Human computer dialogues: https://www.facebook.com/media/set/?set=a.10150196289562090.347036.713727089&type=3#!/photo.php?fbid=10151040516712090&set=a.10150196289562090.347036.713727089&type=3&theater
- Functions of CASE tools: http://www.theecommercesolution.com/usefull_links/case_tools.php
- Observation and document analysis in systems requirements determination: https://www.facebook.com/media/set/?set=a.10150196289562090.347036.713727089&type=3#!/photo.php?fbid=10151040476432090&set=a.10150196289562090.347036.713727089&type=3&theater
- Roles in IS projects
- Gantt chart and work breakdown structure: http://en.wikipedia.org/wiki/Gantt_chart; http://en.wikipedia.org/wiki/Work_breakdown_structure
- Request for proposal
- Rich picture and CATWOE analysis: http://bpmgeek.com/blog/what-catwoe-analysis
- Use Case diagram
- Quality requirement statement characteristics: https://www.facebook.com/media/set/?set=a.10150196289562090.347036.713727089&type=1#!/photo.php?fbid=10151040486842090&set=a.10150196289562090.347036.713727089&type=3&theater
Electronic Commerce textbook mentioned in last workshop: http://www.pearsonhighered.com/educator/product/Electronic-Commerce-2010/9780136100362.page
Work breakdown structures (WBS) are frequently used by project teams to break the project into smaller, easily identifiable components. The WBS structures used in projects follow strict rules like 100% rule and the mutually exclusive rule, but in general, they can be used to break down almost any complex task.
ReplyDelete