What makes software engineering difficult - PowerPoint PPT Presentation

1 / 3
About This Presentation
Title:

What makes software engineering difficult

Description:

Method(ologies) Embody 'best practices' by directly supporting the above ... (ologies) is there and why? Introduction (only) to widely used method(ology) RUP ... – PowerPoint PPT presentation

Number of Views:45
Avg rating:3.0/5.0
Slides: 4
Provided by: mcas8
Category:

less

Transcript and Presenter's Notes

Title: What makes software engineering difficult


1
Initial Considerations Lecture 1 Revisted
  • What makes software engineering difficult?
  • Reasons identified included unlimited number of
    degrees of freedom, lack of universal
    standardised building blocks, not made from
    physical materials by application of physical
    processes, etc
  • Not necessarily the size/scale of the software,
    i.e. we should be able to engineer even the
    smallest software component
  • What makes software engineering easier?
  • Formal notations
  • Enforce a single unambiguous meaning on resulting
    descriptions
  • Automated support (a.k.a. software tools)
  • For specification, design and implementation
    notations languages including editors,
    translators, IDEs, purpose-built tools
  • Shared repositories
  • For project documentation including requirements,
    specifications, designs, development and
    production code, test plans and tests,
    standards
  • Method(ologies)
  • Embody best practices by directly supporting
    the above
  • e.g. RUP (see lecture 2) is use-case driven,
    object-oriented and process oriented

2
Initial Considerations Lectures 2 3 (1)
  • Recall from Initial Considerations (Lecture 1)
    Methods (a.k.a. methodologies) have been
    developed to meet demands made of software
    engineers
  • How do we convert a client's requirements into a
    project that can be successfully completed by a
    team of developers (usually guided by a manager)?
  • Planning and modelling is central to any useful
    method
  • Modern S.E is Process-Oriented
  • Involves iterative incremental development
  • Do we understand these terms correctly?
  • What diversity of method(ologies) is there and
    why?
  • Introduction (only) to widely used method(ology)
    RUP
  • Insufficient time to undertake a complete RUP
    course
  • How are project teams organised?
  • What kind of organisation are we in? (i.e.
    software-engineering-wise)

3
Initial Considerations Lectures 2 3 (2)
  • Software Project Management (oh no! not
    management)
  • Is managing a software project something we can
    learn to do (better)?
  • What is a software project and its management
    plan?
  • How are the components organised and described?
  • How can the progress of a project be formalised?
  • What (formal) standards are involved?
  • If we have to create a software Project
    Management Plan what should it contain (in
    comprehensive detail)
  • Especially Work Breakdown Structures and Work
    Packages
  • and hence
  • Example Project Management Methodology (PRINCE2)
  • Managing requirements
  • To have successful projects that deliver software
    fit for purpose
  • What formalising techniques do we know and when
    are they appropriate to use?
  • How do we know validation is telling us truths?
  • What causes problems when validating software
    systems and why?
Write a Comment
User Comments (0)
About PowerShow.com