e-SEM
 Life cycle    | Phase-neutral themes    | Initiation    | Definition    | Design/Implementation    | Operations    | Termination
Introduction
Goals of e-SEM
How to use
e-SEM
Life cycle
approach
The e-SEM web
Feedback

Goals of e-SEM

e-SEM is a collection of PSE's best practices
The topics and contents covered in e-SEM were drawn up by a working group encompassing representatives of most PSE subdivisions and numerous experts from the Know-how Base (KB). e-SEM reflects PSE's experience and day-to-day practice and is subject to continuous further improvement in line with the latest requirements and insights.

In which projects should e-SEM be used?
Typically, in web projects and in e-business environments. In a wider sense, however, for all other types of development activities featuring the following characteristics:

  • extremely tight schedule, short development cycles
  • unclear requirements at project start time (frequently, no requirements specification is available)
  • close cooperation with the client/end customer and external companies (e.g. design companies)
  • relatively small development teams in most cases
  • high-level technical challenges for the teams (new and often not fully mature development environments)
  • strong design challenges (graphical interfaces, Web user interfaces, usability as a key success factor)
  • rapid establishment/dissolution of teams required
  • work has to "take off" instantly, without a preparatory phase, in an environment of complex application frameworks and continuously changing tools

Exact definitions are hardly possible (and not necessarily useful) for such projects. Using e-SEM is always recommendable when the typical characteristics listed above prevail in a project. In the e-SEM web, such projects are summarily referred to as "e-projects"