Documente Academic
Documente Profesional
Documente Cultură
edu
COMMONWEALTH OF AUSTRALIA Copyright Regulations 1969
www.it.monash.edu
WARNING This material has been reproduced and communicated to you by or on behalf of Monash University pursuant to Part VB of the Copyright Act 1968 (the Act). The material in this communication may be subject to copyright under the Act. Any further reproduction or communication of this material by you may be the subject of copyright protection under the Act. Do not remove this notice.
FIT2001 Systems Development: campus Week 1 Lecturer Sections 2012 by Thomson Course Technology. All rights reserved.
www.it.monash.edu
www.it.monash.edu
Teaching Team
Lecturer: Tutors:
www.it.monash.edu
www.it.monash.edu
Common Core
FIT2001 is a common core unit. The common core is a set of units that will be taken by all undergraduate students studying degrees with the Faculty of Information Technology. It represents the fundamental body of knowledge that we believe all IT professionals require.
Studios
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
Textbooks
Recommended texts:
Satzinger, J. W., Jackson, R.B., Burd, S.D. and R. Johnson (2012) Systems Analysis and Design in a Changing World, 6th Edition, Thomsen Course Technology. Rosenburg and Stephens (2007) Use case driven object modeling with UML theory and practice. Apress. (free e-copy available) Refer to unit information guide
Use case driven object modeling with UML theory and practice
www.it.monash.edu
www.it.monash.edu
Anticipated Workload
2 hour lecture 2 hour per week workshop/tutorial session 6 hours per week preparation and project work 2 hours per week reading
Assessment
40% - Assignments
You must do 2 assignments.
Three assignments available, each worth 20%. Can do more than 2, your best 2 will count.
60% - Examination
Three hour, closed book exam, scheduled during the normal exam period.
www.it.monash.edu
www.it.monash.edu
Plagiarism/cheating
The University and the Faculty have various policies regarding plagiarism that you must make yourself familiar with.
http://www.infotech.monash.edu.au/about/committeesgroups/facboard/policies/academiccheat.html
www.it.monash.edu
www.it.monash.edu
Lecture schedule
Site includes downloads, forums, campus specific information Make full use of this system to get the most out of the unit 1. The development environment 2. Domain modelling with UML 3. Prototyping in analysis and design 4. Process modelling with use case diagrams 5. Interface design principles 6. Usability testing 7. Principles of good design 8. Use case realization with sequence diagrams 9. The requirements specification and RFPS 10.Use case driven testing 11. Requirements gathering and stakeholder expectation management 12. The implementation and support phase
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
Each week, your reading of the texts is vital to achieving the learning objectives.
www.it.monash.edu
www.it.monash.edu
Key concepts
Systems analysis
What system should do
Systems design
How components of information system should be physically implemented
Systems analyst
Uses analysis and design techniques to solve business problems with information technology
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
Many systems analysts will have chosen business electives in their University course
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
Reuse
Building standard solutions and components that can be used over and over again
Methodologies
Include the rules, guidelines, and techniquesthat define how systems are built
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
Example: Outline, rough draft, edited result Example: Blueprint, frame, completed house
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
Models
Representation of an important aspect of real world, but not same as real thing Abstraction used to separate out aspect Diagrams and charts Project planning and budgeting aids
www.it.monash.edu
www.it.monash.edu
Techniques
Collection of guidelines that help analyst complete system development activity or task Can be step-by-step instructions or just general advice
www.it.monash.edu
www.it.monash.edu
CASE tools
Computer-Aided System Engineering (CASE)
Automated tools to improve the speed and quality of system development work Contains database of information about system called repository
Upper CASE - support for analysis and design Lower CASE - support for implementation ICASE - integrated CASE tools Examples include CAs ERWin, IBMs Rational and Visual Paradigm for UML
www.it.monash.edu
www.it.monash.edu
SDLC variations
Many variations of SDLC in practice
No matter which one, tasks are similar
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation
www.it.monash.edu
www.it.monash.edu
Validation
Consider testability Prove model is right with code
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
www.it.monash.edu
Scrum
A quick, adaptive, and self-organizing development methodology
Named after rugbys system for getting an out-of-play ball into play Responds to a current situation as rapidly and positively as possible Empirical process control approach to developing software
Scrum philosophy
Responsive to a highly changing, dynamic environment Focuses primarily on the team level
Team exerts total control over its own organization and work processes
www.it.monash.edu
www.it.monash.edu
Scrum organization
Product owner The client stakeholder for whom a system is being built Maintains the product backlog list Scrum master Person in charge of a Scrum project Scrum team or teams Small group of developers Set their own goals and distribute work among themselves
Scrum practices
Sprint The basic work process in Scrum A time-controlled mini-project Firm 30-day time box with a specific goal or deliverable Parts of a sprint Begins with a one-day planning session A short daily Scrum meeting to report progress Ends with a final half-day review
www.it.monash.edu
www.it.monash.edu
Unified Modeling Language (UML) used primarily for modeling UML can be used with any OO methodology UP defines 4 life cycle phases
Inception, elaboration, construction, transition
www.it.monash.edu
www.it.monash.edu
ICONIX
Agile development method that uses UML
Our focus in this unit Described by the RS text
ICONIX Overview
Focus on early GUI and domain modelling. UML use cases organise detailed design
www.it.monash.edu
www.it.monash.edu
Todays summary
Information systems development is much more than writing programs Systems analyst solves business problems using information systems technology Problem solving means looking into business problem in great detail, completely understanding problem, and choosing best solution
www.it.monash.edu
www.it.monash.edu
Summary (continued)
Systems analyst has broad knowledge and variety of skills, including technical, business, and people Many different paths and approaches to the SDLC Waterfall, overlap, iterative Analysis focuses on what a system has to do Design focuses on how a system is going to do it A methodology is a set of guidelines to follow for completing every SDLC activity
Summary (Cont.)
Adaptive development methodologies Unified Process (UP)! Agile Modelling and Agile Development Extreme Programming (XP)! >Tests are written first; programmers work in pairs Scrum >Defines a specific goal that can be completed within four weeks ICONIX >Early GUI and domain modelling >Development guided by UML use cases
www.it.monash.edu
Verify your understanding of the key terms at the end of SJB chapter 1 Try the week 1 quiz on the Moodle web site