Frequently Asked Questions (F.A.Q.) on stdSEM

Table of contents:

Scope of stdSEM

Does stdSEM interest me at all (SEPP, PHB,...) ?
Does stdSEM not just apply for 30% of the PSE?
The frame phases apply for everyone; a QA plan must always be drawn up, even if the customer method does not require this.

stdSEM is also helpful for a wide range of tasks performed within the framework of other development methods (e.g. PP, QA, annotated checklists for documents which are also needed for other methods).
Is stdSEM to be applied alongside the customer method? The frame phases apply for everyone; a QA plan must always be drawn up, even if the customer method does not require this. Everything else must be processed using the customer method.
What project types (based on PROCON) does stdSEM apply for? ENTW, TOPS, pointers are included for CONS, WART
Is SEM an implicit service instruction? A PSE notification makes SEM mandatory and thereby turns the frame phases into "service instructions"

Questions on the content of stdSEM

Why the need for a new SEM?
  • EHB and EVHB applied for all PSE projects and were therefore automatically very abstract and general. It was proposed with the SEI assessment 1993 that a superordinate process model be used for different platforms or tasks to create instances which yield more specific instructions. This was commenced with SEM VM, stdSEM and eeSEM. ooSEM is currently in development.
  • After more than 10 years, a facelift was necessary, both in terms of content and presentation.
  • It is necessary to move with the needs of the time.
  • The requirements that have been made known to us (feedback from operative businesses) have been taken into account in the stdSEM.
  • The new stdSEM is much closer to actual project activities.
Why do the documents have different structures? We have learned from the experiences gathered over recent years; the structure is now more transparent and easy to use.
Why are there so few examples and reference projects? There are far more examples than in the old SEM; this aspect will be further expanded, however.

If you wish, you can nominate yourself as a reference project; you will then (if you wish) receive greater support in the use and implementation of stdSEM in your project.
Why has the phase subdivision been changed? Frame phases are mandatory for everyone (new in this form);

Phases are subdivided into subphases; the extent to which these are processed explicitly as phases with their own milestones etc. depends on the particular project. The result is better support for tailoring.

Other phases have been grouped together more tightly; the subphases are more flexible, however.
How can I tell what I must/may/should do? From every phase homepage, you can move to the "Phase Orientation" which sets out the degree of obligation relating to the various results.
Why is stdSEM redundant at several points? It is unavoidable in a hypertext, since the sequence in which text is read cannot be predicted.
Why is there no "Contract" result? The contract forms part of the business process and is regulated within this business process; SEM is primarily intended for development work.
Are the tender texts referred to up-to-date? The texts have been checked by the Tax and Law Department and the up-to-date texts placed on the commercial managers' drive (link) by PSE K.
Is stdSEM more effort-intensive than the EVHB used earlier? Probably not; more pages do not mean more specifications, but rather better support; therefore an advantage for developers.

What terms have changed since SEM V 3.0?

stdSEM SEM V 3.0 Reason for change
Deliverables Product structure The old term constantly resulted in misunderstandings, particularly the term "structure". People thought that the software structure of the product was meant. The new term is intended first and foremost to emphasize that it relates to everything which must be supplied.
Additional components Object structure The old term constantly resulted in misunderstandings. As well as the ambiguous term "structure", the term "object structure" also included the term "object" which began to suggest something quite different with the advent of object-oriented technologies.

While the new term is not very "handy", it does specify precisely what is meant. They represent additional components to the deliverables!
Activity planning Project structure planning The old term contained the ambiguous term "structure" and was also continuously confused with the almost identical term "product structure planning". The new term says directly what it is about!
Planning the work sequence Process planning The old term resulted in frequent misunderstandings and led to criticism that processes were actually something quite different than a sequence of events. The new term says exactly what is meant!
Preliminary project plan Short project plan The old term was often confused with the planning for a "short" project. Since it relates to an initial rough plan, the new term is more appropriate.
Architectural design specification System specification The word "system" was interpreted in different ways, often as the totality of HW and SW. The new term expresses more clearly what is meant: A specification which does not go into the implementation details.
Stand-alone test Component test The test does not test a "component" (in addition, the word "component" is used in a number of different ways), instead it involves testing of an as yet unintegrated element.
Development-related product documentation Technical SW documentation The earlier term resulted in misunderstandings (what is actually being supplied?); part of the product documentation is supplied (forms part of the deliverables), while the other part is internal and represents the development-related product documentation.

Changeover procedures

How should I change over from SEM (old) to stdSEM in ongoing projects? As needs dictate; examine the new contents and draw stimulation from them; begin with the contents of individual documents.

You should also use the SEM Coaching Institution!
When must I start processing new projects using stdSEM? Beginning 1 October 97; it will often be expedient to take into account evolved traditions of the Business Unit / Division and, where appropriate, to use standard content for specific sections of the templates (separate templates with familiar macros if absolutely necessary).
How often will new versions of stdSEM appear? Minor changes can be expected every 3-4 months (additions to tips, checklists, FAQs, etc.); more significant changes will appear more rarely as needs dictate (structural changes, new results, deletion of old results, new phase descriptions).
How will I know whether a new version of stdSEM is available? You will be notified by e-mail.
How will I recognize which pages of stdSEM have been changed? The current web contains a version designation. A separate page exists showing the history of changes made (accessed from the home page) and documents the changes to both content and pages.

The old web will be retained.
How should I execute my project if a stdSEM version change occurs during the project? Generally speaking, version changes will be accompanied by new aids (tips, checklists, FAQs, tools), but not by new "must" requirements or document emissions. Consequently, this aspect does not represent any particular problem. What is more, the old version will remain available on the web.

Major changes which would have rendered a version change more difficult did not occur during the last 14 years of the old SEM.

Use the SEM Coaching Institution!
What about feedback, CRs, complaints, etc.? Your active cooperation is requested in this regard!
  • You can e-mail us from the bottom of every page.
  • In addition, a discussion forum is integrated in the stdSEM web.

stdSEM and our customers

Is stdSEM accessible to all corporate customers? stdSEM is freely accessible within the scope of the Group intranet: The promotional effect weighs heavier than the risk of "industrial espionage". This also goes hand-in-hand with the growing call over recent years for greater openness within the Group and can only be positive for our competence image.
How can we explain to customers the advantages which the new SEM offers over the old one? In terms of content, new developments to SW engineering have been incorporated (e.g. different life cycle approaches) in order to make development more specific.

The form is online: Always available, always up-to-date, always quickly at hand.

This means that SEM is being used more and with less effort. This results in better projects and, consequently, better services for our customers.
What documents are available for external customers? A "glossy folder" and this CD-ROM with a demo version of stdSEM are available.

In addition, the process model appeared as a book, published by Vieweg in 1998:  Kaindl/Lutz/Tippold: Methodik der Softwareentwicklung. Vorgehensmodell und State-of-the-Art der professionellen Praxis.

How does the customer access stdSEM? Group customers via the intranet.

External customers only within the scope of cooperation within the project and only following agreement relating to usage restrictions (possibly with off-line version on CD-ROM).

Network capability of stdSEM

What should I do; I cannot take stdSEM with me to meetings like I have been able to do in the past with folders! Everything can be printed out easily and conveniently (PostScript and pdf files with tables of contents, in section form); this is particularly advisable for overviews and abridged versions.

A folder (fold-up brochure) is available along with a CD-ROM which can also be run without a server.
Is it not a disadvantage to use a single screen for both development and using SEM? This also has advantages: The ability to copy with copy-paste; easier to switch with the Alt-Tab key combination.

The pages can also be printed out if necessary.
Help! I am dependent on the network for using stdSEM! This applies today for every project regardless of the development method used.
Help! I have no access to the network! The strategy of PSE is to provide intranet access from every workstation; SCS Plus Back has been concluded.

An off-line version is also available on CD-ROM.
I would like a personal copy with notations Either print out and annotate the text section by section or use electronic bookmarks with notes.
Why is everything Windows-based and why are there only Word for Windows templates? This is not the case. All document templates are also available as FrameMaker files.

Many text systems allow you to import Word or FrameMaker files.

Questions about the new medium

Why are there so many WWW pages? A printed manual with just as many pages would be far less easy to handle; stdSEM has therefore also been implemented as an electronic manual. There is no need to go into great depth throughout. Instead, you can select the precise subject you want (tips, checklist, FAQ, all you have to do is browse, etc.).
Help! I'm "lost in hyperspace"! - How can I find my way around? The structure will become very clear to you after a short familiarization period and there is plenty of support for navigation ("Where am I?" page, header showing the current phase, phase home pages to provide an overview, help pages, search facilities, rapid access to documents, etc.)

Set your own bookmarks!
Where do I find an overview of everything? In addition to the WWW representation, a folder is also available to provide a rapid overview.
Access takes longer than with paper! That's not really true, since searching in particular is far faster and better.
Why are there no project-specific templates? These are not yet supported within the web (since technically relatively effort-intensive); you can naturally still create project-specific templates as in the past!
I don't like using the screen. Why is there so much screen text to read? This is a problem which many people experience (studies have shown that reading on screen takes up to 30% longer). We have therefore modified the text layout accordingly (many intermediate headings, emphasis, short paragraphs, etc.).

Questions about the costs of stdSEM

Why this great effort for developing stdSEM? A good development method saves costs (naturally only if it is used).

A major project failure will cost several times that of the SEM. SEM is vital in all crisis projects. If the broad use of SEM prevents even a single crisis project from occurring, the effort will pay for itself many times over.

SEM is over 10 years old. A facelift in terms of both content and presentation was necessary.
How high are the training costs for the changeover? A short introduction is all that is needed; online tutorials and help pages are also available.

Brushing up and the new motivation which this inspires is worthwhile.
Will SEM training still be available in course form? Yes, a seminar will provide explanations and an opportunity to discuss the method used; it will not be replaced by the new form of presentation.
What about running costs and maintenance costs on the network? A "living process" naturally has its costs; the effort greatly depends on the extent to which feedback and proposals for improvement are provided; PSE QM wants to support a "living process" and wants to make the resources available to do so.

The maintenance costs are recouped by the up-to-date nature of stdSEM (everyone has the new version at the same time).

Printing series of books is no cheaper (one copy for every version) and, moreover, harms our environment.
Using stdSEM is too expensive, particularly the frame phases! It is worth while in the long run. The Initiation phase makes it harder to "slide into" a project, while the Termination phase makes it easier to evaluate the results (actual costing, RR, experiences).

Why stdSEM could be rejected

"Development methods mean unnecessary bureaucracy!" The graphical appearance and online availability mean that the new SEM is actually far less bureaucratic than the old one; we have attempted to put bureaucracy as far into the background as possible.
"SEM is academic and has little to do with reality!" Checklists, examples, tips and FAQs are far more specific than in the past.
"The framework is too tight!" No-one should enter into a "dangerous practice" without reflecting on the situation (even if a development method is complied with on only a rudimentary level, it will nevertheless still help reduce risks). The specified structure is intended as a support to guide you through the project.

A method is always the described "best practice".
"Business is quite different in reality!" That is true in part, but the development method should also provide a framework for shaping reality ("this would be the ideal situation; if things are not like that, weigh up the risks," etc.) What is more, through using alternative life cycle approaches, for example, we have adopted a closer approach to reality than in the past.

The requirements that are known to us have been integrated into stdSEM.
"Small projects are not supported!" A manual for use with small projects and special templates for these are in preparation (basis is provided by the small project plan; provisional results of the SEM specialist circle for small projects).

Notes are already available for adapting stdSEM to small projects.
"I do not have the time to worry about yet another development method; my job is to develop!" stdSEM is very similar in content to SEM V3; the effort in familiarizing yourself with the new version is less than initial impressions might suggest.

A methodical approach always saves time!

(Do you push your bicycle just because you do not have time to climb onto it?)
"stdSEM contains too many 'musts'!" There are not many more than required by ISO 9001.

In addition, things can be made easier by the ability to group documents together, e.g. in small projects.
"Something else new!" The last update of SEM was in 1992.

An update was necessary (content).

The availability of stdSEM on the intranet and in hypertext form is a real improvement for users. You should actually be pleased about it!

stdSEM and PROCON

What does stdSEM have to do with PROCON? Refer to the notes in the stdSEM folder for an account of the stdSEM specifications in PROCON.

The stdSEM web and the QM pages also contain notes on using PROCON.

stdSEM and CMM Level 3

Are the requirements of CMM level 3 covered by stdSEM? stdSEM covers CMM level 2 in full. A number of additional area-specific procedures are required for level 3 (having the stdSEM development method cover all CMM level 3 requirements is not expedient and would greatly restrict the Divisions).

Additions are easier than in the old SEM.

Siemens AG Österreich, Program and Systems Engineering PSE
Contact: stdSEM Webmaster
Last modified: 08/27/98 16:52
Copyright © Siemens AG Österreich 1997. All rights reserved.