Learning Center
Plans & pricing Sign in
Sign Out
Get this document free



									Chapter 1

   1. Systems, information systems, types of information systems
      What is system? Sub, super?
      What is information system?
      Types: Transaction processing systems
              Management information systems
              Executive information systems
              Decision support systems
              Communication support systems
              Office support systems

   2. Analyst’s skills, knowledge, and activities.
              Technical knowledge and skills
                         Fundamental: computers
                                         OO programming languages and class libraries
                                         OS and utilities
                         Tools: IDEs sun one studio for java or Microsoft visio studio .net for vb .net and
              c# .net
                                  Program cold generators, testing tools, documentation support tools,
              project management tools and so on
                         Techniques: Project planning
                                         Cost/benefit analysis
                                         Requirements modeling
                                         Architectural analysis
                                         Network configuration
                                         Database design

               Business knowledge and skills:
                      Business functions
                      Organization structured
                      Organization managed
                      What type of work: finance, MFG, marketing, customers service and so on

                        Type of org
                        What makes it success ful?
                        Strategy plan
                        Tradition and values
           People knowledge and skills:
                   React to change
                   Work (in a variety of jobs and levels)

           Job titles:
                    Programmer analyst
                    Business system analyst
                    System liaison
                    End-user analyst
                    Business consultant
                    System consultant
                    System support analyst
                    System designer
                    System architect
                    Web master
                    Web developer

3. Problem solving
   Analyst approach to problem solving: problem->benefits->requirements->solutions->decide-
   >detailed solution->implement->monitor and make sure
Chapter 2
       Predictive approach
                       Project planning phase, analysis phase, design phase, implementation
       phase, and support phase
       Adaptive approach:
               Newer: some iterations plan-> analysis and design -> construct first
       prototype-> test and integrate->plan next

       UP SDLC : inception. Vision, business case, scope cost and schedule

               elaboration, refine vision, requirements, scope, design and implement the core
       architecture and functions, resolve high risk, product realistic estimates for cost and

               construction, iteratively implement the rest of lower risk, predictable, and
       easier elements, and prepare for deployment

               transition, beta test and development.

2. Tools, techniques, methodologies

       Tools: software support for models and other components

               PM app

               Drawing / graphics app

               Word processor/text editor

               CASE TOOL


               DBM app

               Reverse-engineering tool

               Code generator tool

              Automated testing tool
       Techniques: a collection of guidelines that help an analyst complete a system
development activity or task.
              Strategic planning
              Project scheduling
                 cost-benefit analysis
                 user interviewing
                 domain modeling
                 use case modeling
                 user interface design
                 RDB design
                 Security design
                 Guidelines to follow for completing every activity in systems development,
including specific models, tools, and techniques.
                 Contains how to use models, tools, and techniques

3. UP disciplines
   OO system development methodology.
   Business modeling
       Business env
       System vision
       Business models
       Gather detailed information
       Functional/nonfunctional requirements
       Prioritize requirements
       Development UI dialogs
       Evaluate requirements with suers
   Design – high level design
       Design the support services architecture and deployment env
       Design the software architecture
       Design use case realizations
       Design the database
       Design the system and user interface
       Design the system security and controls
       Build software components
       Acquire software components
       Integrate software components
       Define and conduct unit testing (functionality of software components)
       Define and conduct integration testing (components works together)
       Define and conduct usability testing (ease of use)
      Define and conduct user acceptance testing (system is built)
      Acquire hardware and system software
      Package and install components
      Train users
      Convert and initialize data
   Configuration and change management
      Develop change control procedures
      Manage models and software components
      Finalize the system and project scope
      Develop the project and iteration schedule
      Identify project risks and confirm the project’s deasibility
      Monitor and control the project’s plan. Schedule, internal and external communication
   and risk and outstanding issues
      Select and configure development tools
      Tailor the UP development process
      Provide technical support service

4. OO overview, concepts
   OO approach
   OO A&D
   OO Programming writing statements in a programming
   Class of object - reuse

   Objects – attributes and behaviors
   Attributes –object characteristics that have values
   Methods – behaviors or operations that describe what an object is capital doing
   Classes -classification to which all similar objects belong
   Instances-synonym for object
   Object interactions and messages
   Associations and multiplicity (number of ) – relationship between objects
   Encapsulation (attribute and method combined)and information hiding - hide internal
   Inheritance (one class take on characteristics of another class and extend them) and

5. Objects

   A thing the computer system that can response to messages
Chapter 4

   1. Requirements discipline
             Gather detailed information
                      From people who will be using the system
                      By review planning documents and policy statements
                      Also, what other companies have done
                      Talk to everyone who will use, read everything about existing system (technical
             Define requirements
             Prioritize requirements
             Development user interface dialogs
             Evaluate requirements with users

   2. System requirements

   3. Models

   4. Information gathering
Chapter 7

   1. Design discipline
Chapter 11

   1. User interface design
   2. HCI metaphors
Chapter 13

   1. Testing
   2. Configuration management

To top