SAD281

• SAD 281

  • IMPORTANT INFORMATION
  • DURATION: 2 weeks
  • ASSESSMENTS: 3 assignment/projects, 2 tests, 1 exam
  • CT: 40, Project M1: 50, Project M2: 150, Total: 150
• The design of many software applications begins as a vital image in the minds of its designers
• At first it isn't so bad. Over time as the rotting continues, starting from code disorganization until it gets to the design of the application. The program becomes a mass of code that the developers find increasingly hard to maintain.
• Symptoms of Rotting Designs

  • Rigidity
  • Fragility
  • Immobility
  • Viscosity

  
• Rigidity


  The tendency for software to be difficult to change, even in simple ways
• Fragility


  The tendency of the software to break in many places every time it is changed
• Immobility


  The inability to reuse software from other projects or from parts of the same project
• Viscosity


  Comes in two forms: viscosity of the design, and viscosity of the environment (hacks or changes that do not preserve the design)
• Systems Analysis and Design

  The intent is to obtain well-designed and well-functioning suitable systems and by doing so, to reach business or functional goals
• Systems Analysis


  A professional discipline that studies systems and their environment in order to adapt them (as well the system as its environment), or it studies an environment in order to conceive and build a new system or systemic solution
• What is Software - Class Discussion

  1. Define software in a layman sense

  2. Define software as a programmer

  3. Give examples

  4. How does your knowledge as a programmer or developer change how you view software

  5. What could go wrong with software, do a google search on some software gone bad and how much it affected the organization and its customers in SA

  6. Who's fault was it?
• Systems Analyst


  • An individual who uses analysis and design techniques to solve business problems using I.T.
  • Acts as a bridge between the technical team and the end-users or stakeholders, ensuring that the software meets the needs and requirements of the intended users
  • Duties include: Act as change agents who identify the organizational improvements needed, Design systems to implement changes, Train and motivate others to use the systems
• Notable software glitches that occurred in 2010

  • Verizon Wireless had to refund $50 million to customers due to billing system error
  • Toys R Us system double billing shoppers on Black Friday
  • Navy Drone Violated Washington Airspace
• Many failed systems were abandoned because the analysts tried to build a wonderful system without clearly understanding how the system would: Support the organization's goals, Improve business processes, and Integrate with other information systems to provide value
• A Systems Analyst's Skills

  • Technical
  • Business
  • Analytical
  • Interpersonal
  • Management
  • Ethical
• Technical Skills


  Must understand the organization's existing technical environment, the new system's technology foundation, and the way in which both can be fit into an integrated technical solution. Example: Microsoft Access, Integrated development environments, computer-supported system engineering (CASE) tools
• Business Skills


  Understand how IT can be applied to business situations and to ensure that the IT delivers real business value. Example - Industry Understanding, Business Processes, Communication, Teamwork, Finance etc
• Analytical Skills


  Analysts must be continuous problem solvers at both the project and the organizational level, and they put their analytical skills to the test regularly. Example: Problem Identification, Requirement Analysis, Data Analysis, Risk Assessment
• Interpersonal Skills


  Need to communicate effectively, one-on-one with users and business managers (who often have little experience with technology) and with programmers
• Management Skills


  Need to manage people with whom they work, and they must manage the pressure and risks associated with unclear situations
• Ethical Skills


  Must deal fairly, honestly, and ethically with other project team members, managers, and system users. Must deal with confidential information. It is important for analysts to maintain confidence and trust with all people
• Systems Development Life Cycle (SDLC)

  The process of determining how an information system (IS) can support business needs, designing the system, building it, and delivering it to users

  
• Systems Development Life Cycle (SDLC)

  1. Planning phase

  2. Analysis phase

  3. Design phase

  4. Implementation phase