|
||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
Systems Analysis and Design
Author:Patricia O'Byrne Description:This module teaches intermediate systems analysis and design. The student will learn an object-oriented methodology and apply its techniques. The student will learn to develop a 3-tier system from a simple case study. Object-oriented techniques such as patterns, refactoring, testing and package design are covered in a theoretical way. Aim:The aim of this module is to equip the student with the necessary knowledge, skills and experience to enable them to function as a junior software developer within a software development project team. Learning Outcomes:On completion of this module, the learner will be able to
Learning and Teaching MethodsThis module is taught through lectures and exercises in class combined with practical application through use of web and CASE tools.
Module ContentIntroduction: Information systems types and components including personnel from a developer’s perspective, the role and requirements of an information system development methodology. Review of the historical evolution of information systems development methodologies and the traditional systems development life cycle. Accessibility Challenges for Systems Development Popular Methodologies: General study and appraisal of popular methodologies, including common and specific techniques used; emphasis to be placed on the design phase. Case Study: The student will undertake an assessable case study, ideally as part of a group. Object Oriented Analysis and Design Methodology: Concepts, class and object models, notation; OO analysis, identifying objects, attributes, operations and inter-object communication; classification and assembly structures, instance connections, data modelling; OO design, objects, operations, messages, descriptions; classes, instances and inheritance, class and object relationship and notation; design steps; OO design and structured methods. Specialised Methodologies: Overview and appraisal of methodologies such as Rational Unified Process, Information Engineering, Jackson Systems Development, Soft Systems Methodology. Choosing a Methodology: Sources, comparing, limitations, adopting. Development Tools: CASE tools for project management, systems support, analysis, design, prototyping, programming and testing; integrated CASE environments. Module AssessmentWritten Examination - 70% Continuous Assessment (Case Study) (30%) Essential ReadingAvison & Fitzgerald (2003), Information Systems Development, 2nd Ed. McGraw-Hill
Supplemental ReadingR Pressman (2005), Software Engineering: A Practitioner’s Approach, 6th Edition, McGraw Hill "Object-Oriented Systems Development a gentle introduction" Britton, Doake, McGraw Hill, 2000. "UML distilled Applying the standard object modeling language" Fowler, Scott, Addison Wesley Object Technology series, Update Edition 2000. "Using UML Software Engineering with Objects and Components" Stevens, Pooley, Addison Wesley Object Technology series, Update Edition 2000. "The Rational Unified Process, An Introduction." Kruchten, Addison Wesley Object Technology series, 2nd Edition 2000. "Visual Modelling with Rational Rose 2000 and UML", Quatrani, Addison Wesley Object Technology series, 2000. "Software System Development a gentle introduction" 3rd. Ed.Britton, Doake, McGraw Hill, 2003. "Structured Systems Analysis and Design Method - Application and Context", Downs, Clare & Coe, 2nd Ed. Prentice Hall, 1992. "The Rational Unified Process, an introduction", Philippe Kruchten, 2nd Ed. Addison Wesley Object Technology series, 2000. "Core J2EE Patterns" 2nd Ed. Alur, Crupi, Malks, Prentice Hall, 2003. "Object-Oriented Reengineering Patterns", Demeyer, Ducasse, Nerstrasz, Morgan Kaufmann, 2003 "Refactoring: improving the design of existing code", Fowler, Addison-Wesley, 2000
Web references, journals and other:See module web page for details. National Disability Authority WWW.NDA.IE Trace Center Wisconsin http://trace.wisc.edu
Further Details:one hour practical 1hour tutorial (first semester) and one hour lecture per week. Two semesters- long module. Date of Academic Council Approval:June 2005
|