|
1. Aims
On successful completion of this subject a student will be:
- knowledgeable in the theory of "structured systems" analysis and conversant in its terminology;
- experienced in the production of Systems Requirements and Design specifications;
- capable of evaluating alternative physical implementations of a system;
- familiar with CASE and other technologies relevant to systems analysis;
- aware of alternative approaches to systems analysis, in particular object-oriented techniques; and<
- conscious of the ethics of professional systems analysis.
In particular, a student will be competent in:
- gathering data to identify business requirements;
- translating business needs into technical requirements;
- matching IT needs with the strategic direction of an enterprise; and
- validating the quality and completeness of design specifications.
2. Content
2.1 Introduction to systems analysis
An introduction to the environment in which systems analysis takes place. The student will appreciate that not all problems are technical, therefore both technical and social goals must be satisfied. Both are closely correlated such that available technical systems often influence social structures.
2.2 Information systems
Business applications that use computers are covered. Almost all information systems are built to help the processing of information within business entities, so it is important for a systems analyst to understand business organisations and the way that they operate.
2.3 Information gathering
Obtaining information can be a very complicated process and it is important to follow an organised strategy. When analysing an information system there are many sources of relevant information and many methods by which to acquire it.
2.4 Systems development life cycle
The concept of a life cycle applies to many natural and man-made systems. Development of an information system also involves progressing through a certain life cycle. A need to organise systems analysis activities is covered, including various ways of organising such activities and why different ways may suit different types of problem.
2.5 Process modelling
An information system is composed of, as a minimum, data and processes. A data flow diagram is a model of the process components. The concept of logical and physical models and different approaches to process modelling are covered.
2.6 Data modelling
A data model is a map of data kept in a system. It is used to navigate among data stores and so supply information required by a user. An analyst needs to be aware that a change in one place in a system may affect an outcome at in a different place. A data model provides a structural view of an information system.
2.7 Process Description
Describing a process unambiguously to both developer and user is a balancing act. The analyst must use methods with which a programmer is familiar, but not confuse a user. Techniques of structured English, decision tables and decision trees are covered.
2.8 Object modelling
Object-oriented modelling is a relatively modern approach to systems analysis. Object-orientation is an integrative paradigm and its methods may be used to combine different views of a system, such as the functional view provided by process modelling and the structural view provided by data modelling.
2.9 Quality assurance
With the increasing complexity, sophistication and cost of information systems development, quality assurance is a topic of vital importance in systems analysis. It involves ensuring that a system will satisfy user requirements, that documentation does not contain errors and omissions and that a system will be relevant and contribute to the effectiveness of an organisation.
Allied with quality assurance is professional ethics. The handbook of the Australian Computer Society states that a computer professional will be honest, forthright and impartial, will serve with loyalty employers, clients and the public, will strive to increase the confidence and prestige of the profession and will use special knowledge and skill for advancement of human welfare.
2.10 Documentation
Methods of keeping track of work undertaken during systems analysis and development are covered, including necessity for a documentation standard and a need for a system repository. Incorporating a data dictionary and process specification, a system repository is essential documentation for any information systems development. It can be considered as a modelling tool in the same way as data flow diagrams, entity relationship diagrams and object diagrams. However it is not graphical and, compared to other tools, contains much more detailed information.
2.11 Designing a new system
A set of steps to follow and possible techniques by which an analyst may seek solutions are covered. Objectives focus design so as to meet specific requirements.
2.12 Productivity tools
The advent of Computer Assisted Software Engineering (CASE) tools has reduced time needed to draw diagrams and increased the quality of analysis. A CASE tool integrates models and a system repository to improve quality throughout the Systems Development Life Cycle.
2.13 Project planning
An overview of major issues associated with project planning on systems analysis is covered. The purpose of project management is to ensure that a project is completed in the most effective manner.
2.14 Strategic management
An overview of major issues associated with the influence of strategic management on systems analysis is covered. A strategic plan is needed to ensure that resources are made available for future systems development.
3.Assessment
Assessment in this subject aims, first and foremost, to ensure a candidate satisfies the requirements specified in the following Units of Competency;
3.1 ICAA5151B Gather Data To Identify Business Requirements, and in particular, the following Elements of Competence
- Identify key information sources
- Gather data through formal processes
- Ensure analysis is accurate and complete
- Gain consensus
3.2 ICAA5158B Translate The Business Needs Into Technical Requirements, in particular
- Identify business needs
- Identify requirements
- Sign off on technical requirements
3.3 ICAP5039B Match The IT Needs With The Strategic Direction Of The Enterprise, in particular
- Evaluate current business strategy
- Evaluate the impact of changes
- Develop action plans
3.4 ICAA5054C Validate Quality And Completeness Of Design Specifications, in particular
- Determine audit criteria
- Determine all aspects of a final system
- Review and confirm with contract and specifications
4. Notes
Successful candidates will have practical skills sufficient to demonstrate how systems techniques can be applied to a case study. It is recommended that topics are covered with reference to a realistic case study that incorporates opportunities for role-playing.
With an increasing use of CASE tools for systems analysis, it is important that candidates gain hands-on exposure to appropriate software. A suitable case tool should contain, in addition to diagramming facilities, some form of system repository.
In addition to practical skills, successful candidates will have a sound understanding of underlying theories. It is suggested that, in addition to the principal text, student read extensively from other systems analysis texts, such as those provided in the reference section.
5. Text
The text is:
- Systems Analysis and Design in a Changing World, 5th ed, Satzinger, John W., Jackson, R.L., and Burd, S.D., Cengage Learning, 2008, ISBN 13-978-1-4239-0228-7 To review or purchase this textbook click here
6. References
- Booch, G., Rumbaugh, J. & Jacobson, I. The Unified Modeling Language user guide. Reading, MA, Addison Wesley Longman, Inc., 1999.
- Burch, J.G., Systems analysis, design and implementation, Boyd & Fraser, Boston, 1992.
- Davis, W.S., The information system consultant's handbook: systems analysis and design, Boca Raton, FL, CRC Press, 1998.
- Fertuck, L., Systems analysis and design with modern methods, Dubique, IA, Business and Educational Technologies, 1995.
- Fisher, A.S., CASE: Using software development tools, 2nd edn., Wiley & Sons, 1991.
- Garner S., Systems Analysis and Design with ASCENT, Knowledge base, PO Box 304, Greenwood, Western Australia, 2000.
- Henderson-Sellers, B., A book of object-oriented knowledge, Prentice-Hall, Upper Saddle River, New Jersey, 1997.
- Hoffer, J.A., George, J.F. & Valacich, J.S., Modern systems analysis and design, Reading, MA, Addison-Wesley, 1999.
- Kendall, K. E. & Kendall, J. E., Systems analysis and design, Upper Saddle River, NJ, Prentice-Hall, 1999.
- Kendall, P .A., Introduction to systems analysis and design, 2nd edn., Wm. C. Brown, 1992.
- Odell, J. J., Advanced object-oriented analysis and design using UML, Cambridge, NY, Cambridge University Press, 1998.
- Powers, M.J., Cheney, P.H. and Crow, G., Structured systems development: Analysis, design, implementation, 2nd edn., Boys and Fraser, Boston, 1990.
|
