• Like
  • Save
FIT2001 Week 1
Upcoming SlideShare
Loading in...5
×

FIT2001 Week 1

  • 268 views
Uploaded on

The slides I used in the first lecture for FIT2001, semester 1, 2008 at Caulfield.

The slides I used in the first lecture for FIT2001, semester 1, 2008 at Caulfield.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
268
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. COMMONWEALTH OF AUSTRALIA Copyright Regulations 1969
    • 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.
    www.monash.edu.au
  • 2. FIT2001 Systems Analysis and Design: Caulfield Week 1 Peter O’Donnell Sections © 2006 by Thomson Course Technology. All rights reserved.
    • The nature of systems analysis and design
    www.monash.edu.au
  • 3. Overview of today’s lecture
    • Introducing the academic staff
    • Unit objectives
    • Semester structure
    • Text book and workload
    • Assessment
      • Plagiarism
    • The nature of systems analysis and design
    www.monash.edu.au
  • 4. Academic staff
    • Peter O’Donnell
      • Room: H7.39
      • Phone: 9093 2502
      • [email_address]
    • David Grant
      • [email_address]
    • Jacob Zhivov
      • [email_address]
    • Find us all on Facebook too!
    www.monash.edu.au
  • 5. Lecture and studios
    • Lecture
      • Tuesday: 10am, H1.26
    • Studios
      • Tuesday: 12 noon, K1.07, K1.08 and K1.10; 2pm, K1.08; 4pm K1.08
      • Wednesday : 10am, K1.10; 12 noon, K1.07.
    www.monash.edu.au
  • 6. 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.
    www.monash.edu.au
  • 7. FIT2001 Philosophy
    • There is an increasing need for graduates to understand the fundamentals of systems analysis and design. FIT2001 offers theoretical knowledge and practical application of the area of systems analysis and systems design to enable students to be competitive and informed in their further study or future employment.
    www.monash.edu.au
  • 8. FIT2001 Unit Objectives
    • Knowledge and understanding
      • Describe the roles of systems analysts and designers and their role in system development
      • Describe various system development methodologies
      • Distinguish the processes of systems analysis and design in structured and object-oriented systems development methodologies and life-cycles
      • Undertake planning and problem definition in simple information technology problems
    www.monash.edu.au
  • 9. FIT2001 Unit Objectives (Cont.)
    • Knowledge and Understanding (Cont.)
      • Apply principles of systems design, and explain the relationship of systems design to systems analysis
      • Understand the criteria that can be used to evaluate the quality of a model of a system.
      • Explain the purpose of different types of models in the UML
      • Explain the role and application of automated tools in systems modeling.
    www.monash.edu.au
  • 10. FIT2001 Unit Objectives (Cont.)
    • Attitudes, Values and Beliefs
      • Appreciate that a range of valid solutions exist for any given problem.
    • Relationships, Communication and Team Work
      • Explain the interdependence and relationships between all stake-holders in the systems development process.
    • Practical Skills
      • Model and design logical and physical systems using industry standard object oriented techniques
      • Interpret and evaluate systems analysis and systems design models created using both structured and object oriented techniques.
    www.monash.edu.au
  • 11. FIT2001 Unit Objectives (Cont.)
    • Practical skills (Cont.)
      • Create analysis and design models using the main elements of the unified modelling language (UML)
      • Develop and practice the skills and competencies necessary to undertake a requirements analysis for a business application
      • Apply problem solving techniques at different levels of abstraction and understand the effect this may have on a system specification
    www.monash.edu.au
  • 12. Textbooks
    • Prescribed text:
      • Satzinger, J. W., Jackson, R.B., Burd, S.D. and R. Johnson (2006) Systems Analysis and Design in a Changing World, 4th Edition, Thomsen Course Technology.
    • Recommended texts:
      • Refer to unit information guide
    www.monash.edu.au
  • 13. Systems Analysis and Design in a Changing World
    • You simply must get a copy
    www.monash.edu.au
  • 14. 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
    www.monash.edu.au
  • 15. Assessment
    • 40% - Assignments
    • 60% - Examination
      • Three hour, closed book exam, scheduled during the normal exam period.
    www.monash.edu.au
  • 16. Assignment work
    • Shoe store case study: Inventory management system
      • An audio (.mp3) file
    • Requirements specification:
      • Assignment 1a, 5%, midnight, April 13.
      • Assignment 1b, 20%, midnight, May 4.
    • Design specification:
      • Assignment 2, 15%, due midnight, May 25.
    • Optional bonus requirement:
      • Weekly reflective blogs (3% added to assignment mark)
    • Details available on unit web site (Moodle not MUSO)
    www.monash.edu.au
  • 17. Moodle (moodle.med.monash.edu.au)
    • Open source learning environment
    • Trial hosted by Faculty of Medicine
    • Site includes downloads, forums, blogs,podcast, campus specific information
    • You must make full use of this system to get the most out of the unit
    www.monash.edu.au
  • 18. 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/committees-groups/facboard/policies/academiccheat.html
    www.monash.edu.au
  • 19. Lecture schedule
    • Introduction to Systems Analysis and Design
    • The Context of Analysis and Design
    • Requirements Gathering
    • Beginning Analysis
    • Structured Analysis
    • Use Case Modelling
    www.monash.edu.au
    • Finishing Analysis
    • The Nature of Good Design
    • Structured Design
    • Use Case Realization
    • User Interface Design
    • System Interfaces
    • Unit Review
  • 20. This week’s learning objectives
    • On completion of this your study this week you should aim to be able to:
      • Explain the vital role of a systems analyst in the development of information technology systems.
      • Describe the role of the systems analyst in a systems development project.
      • Describe the types of systems that an analyst might help to create.
      • Describe the types of technology that an analyst needs to understand.
    www.monash.edu.au
  • 21. Learning objectives (continued)
    • On completion of this week you should aim to be able to (cont.):
      • Describe the various job titles that are applied in different work places for the role of analyst and designer
      • Explain the importance of technical, people business and analytical skills for an analyst.
      • Explain why ethical behaviour is crucial for a systems analyst.
    • Each week, your reading of the text is vital to achieving the learning objectives.
    www.monash.edu.au
  • 22. The nature of systems analysis and design
    • Information Systems
      • Crucial to success of modern business organizations
      • Constantly being developed to make business more competitive
      • Impact productivity and profits
    • Keys to successful systems development
      • Thorough systems analysis and design
      • Understanding what business requires
    www.monash.edu.au
  • 23. Overview
    • 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.monash.edu.au
  • 24. The analyst as a business problem solver
    • Has computer technology knowledge and programming expertise
    • Understands business problems
    • Uses logical methods for solving problems
    • Has fundamental curiosity
    • Wants to make things better
    • Is more of a business problem solver than technical programmer
    www.monash.edu.au
  • 25. Analyst’s Approach to Problem Solving www.monash.edu.au Verify that the benefits of solving the problem outweigh the costs Research and understand the problem Define the requirements for solving the problem Develop a set of possible solutions (alternatives) Define the details of the chosen solution Monitor to make sure that you obtain the desired results Decide which solution is best, and make a recommendation Implement the solution
  • 26. Systems that solve business problems
    • System – interrelated components functioning together to achieve outcome
    • Information systems – collection of interrelated components that collect, process, store, and provide as output information needed to complete tasks
    • Subsystems – part of larger system
    • Supersystem – larger system contains subsystem
    • Functional decomposition – dividing system into smaller subsystems and components
    www.monash.edu.au
  • 27. Required skills of the systems analyst
    • An analyst should have fundamental technology knowledge of:
      • Computers / peripheral devices (hardware)
      • Communication networks and connectivity
      • Database and database management systems (DBMS)
      • Programming languages (for example: VB.NET or Java)
      • Operating systems and utilities
    www.monash.edu.au
  • 28. Technical knowledge and skills
    • Analyst uses tools:
      • Software productivity packages (MS Office)
      • Integrated development environments (IDEs) for programming languages
      • CASE tools / coding, testing, and documentation support packages
        • For example rational Rose and Sybase PowerDesigner
    • Analyst understands SDLC phase techniques:
      • Project planning
      • Systems analysis, systems design
      • Construction, implementation, systems support
    www.monash.edu.au
  • 29. Business knowledge and skills
    • Analyst must understand:
      • Business functions performed by organization
      • Organizational structure
      • Organization management techniques
      • Functional work processes
    • Systems analysts will have chosen business electives in their University course
    www.monash.edu.au
  • 30. People knowledge and skills
    • Systems analysts need to understand how people:
      • Think, learn, react to change, communicate, work (in a variety of jobs and levels)
    • Interpersonal and communication skills are crucial to:
      • Obtaining information,motivating people, getting cooperation, understanding the complexity and workings of an organization in order to provide necessary support
    www.monash.edu.au
  • 31. Integrity and Ethics
    • Analyst has access to confidential information such as salary, an organization’s planned projects, security systems, etc.
      • Must keep information private
      • Any impropriety can ruin an analyst’s career
      • Analyst plans security in systems to protect confidential information
    www.monash.edu.au
  • 32. The environment surrounding the analyst
    • Types of Technology Encountered
      • Desktop
      • Networked desktops
      • Client-server
      • Mainframe
      • Internet, intranet, and extranet
      • Wireless, PDAs, Cell Phones (mobile workers)
    www.monash.edu.au
  • 33. Typical job titles and places of employment
    • Job titles of systems analyst vary greatly, but entail same thing
    • Places of employment vary from small businesses to large corporations
    • Analysts can be internal employees or outside consultants
    • Analysts can be developing solutions for internal business managers or for external clients and customers
    www.monash.edu.au
  • 34. The analyst’s role in strategic planning
    • Special projects affecting executives
      • Business process reengineering – radical improvements to existing processes
    • Strategic planning development process
    • Information systems strategic planning
      • Application architecture plan (business focus)
      • Technology architecture plan (infrastructure focus)
    • Enterprise resource planning (ERP) integrated systems
    www.monash.edu.au
  • 35. Today’s summary
    • 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
    • Information systems development is much more than writing programs
    www.monash.edu.au
  • 36. Summary (continued)
    • System - collection of interrelated components that function together to achieve some outcome
    • Information systems outcome: solution to a business problem
    • Information systems, subsystems, and components interact with and include hardware, software, inputs, outputs, data, people, and procedures
    www.monash.edu.au
  • 37. Summary (continued)
    • Systems analyst has broad knowledge and variety of skills, including technical, business, and people
    • Integrity and ethical behavior are crucial to success for the analyst
    • Systems analyst encounters a variety of rapidly changing technologies
    • System analyst works on strategic plans and then systems development projects
    www.monash.edu.au
  • 38. Before next week
    • Get a copy of the text book SJB.
    • Read SJB chapter 1
      • Pay attention to the Rocky Mountain Outfitters case study
    • Verify your understanding of the key terms listed on p30 of SJB
    • Attempt the ten thinking critically exercises at the end of SJB.
    • Try the week 1 quiz on the Moodle web site
    www.monash.edu.au