Aula 11 23052013 sii-v1

778 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Aula 11 23052013 sii-v1

  1. 1. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial1Class 11Planning of Information Systems ProjectsAno 2013Sistemas de Informaçãopara a IndústriaAntónio GriloProf. Auxiliar FCT-UNL,
  2. 2. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial2Planning Information Systems ProjectsRunaway projects and system failure represent nearly 30% - 40% of ITprojects:• Exceed schedule, budget• Fail to perform as specified• Types of system failure• Fail to capture essential business requirements• Fail to provide organizational benefits• Complicated, poorly organized user interface• Inaccurate or inconsistent data
  3. 3. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial3Project ManagementProject management activities include planning work, assessing risk,estimating resources required, organizing the work, assigning tasks,controlling project execution, reporting progress, analyzing results.Project management includes five major variables:• Scope• Time• Cost• Quality• Risk
  4. 4. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial4Planning an Information Systems ProjectProject Charter - is a document that is elaborated in order to summarisethe project main goals and scope and obtain a formal approval for thedevelopment of project or phase.Project Preliminary Plan - is a dynamic document that is progressivelydeveloped as the project matures and information becomes available. Thispreliminary plan is included within the business case and takes effect whenthe business case is accepted. The preliminary plan provides direction andcontrol of project activities until a more comprehensive plan can bedeveloped and approved. The preliminary project plan will evolve to theBaseline Project PlanBaseline Project Plan – Is the consolidation of the Project Preliminary Planand will be the basis for the Execution phase of projects
  5. 5. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial5Structure of a Project Plan (Preliminary or Baseline)1. The project background and reason for existence2. The project objectives and success criteria3. The project scope and high level work breakdown structure4. Project schedule detailing key activities and major milestones5. Structure for the management, responsibilities, accountabilities6. Estimate of costs/Budget7. Out of scope items, related projects, constraints, and assumptions8. Impacts, both internal and external9. Risks and response strategy10. Procurement strategy11. Stakeholders Management
  6. 6. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial6Work Breakdown Structure (WBS)
  7. 7. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial7Schedule and Milestones (Gantt Diagram)
  8. 8. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial8Specification of RequirementsSpecifications are intended to a diverse audience- Customers and users for validation, contract, …- Systems (requirements) analysts- Developers, programmers to implement the system- Testers to check that the requirements have been met- Project Managers to measure and control the projectDifferent levels of detail and formality is needed for each audience.There are different templates for requirements specifications (e.g. IEEE830)Requirements = services the system is expected to provide +constraints placed on the systemRequirements engineering = gathering, negotiating, analyzing, anddocumenting requirements
  9. 9. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial9RequirementsThe requirements could be expressed at various levels of abstraction.The way requirements are defined has a major impact on thedevelopment of the information system.Extract from the requirements specification example:R1: The system shall provide illumination of at least 500 candela.R2: The system shall fit within a cube with maximum width of 15cm.R3: The illumination can be switched on and off by a human operator.R4: The system shall respond to operator input within 0.5 seconds.R5: The system shall have a built-in power supply which should becapable of maintaining continuous illumination for at least 4 hours.etc . . . . . . .
  10. 10. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial10Classification of RequirementsUser requirementsHigher level description of services requested and constraints imposed.Should be understood by the user, and should not address design andimplementation aspects. Theyshould focus on the key facilities required.System requirements:A more detailed, structured description of services and constraints.Typically consider the non-functional requirements. They are used bydevelopers as basis for design, and may be specified using variousmodels (object-oriented models, data-flow diagrams, formal specs,etc.). These requirements should indicate WHAT the system is requiredto do (not HOW) and under what conditions and constraints
  11. 11. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial11Requirements
  12. 12. Sistemas de Informação para Indústria© António Grilo 2013Departamento de Engenharia Mecânica e Industrial12Requirements

×