Re: Preparation for a phone screen interview

Subject: Re: Preparation for a phone screen interview
From: "Diane Evans" <diane_evans -at- hotmail -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Sat, 04 Jan 2003 14:43:11 -0800


What are the main documents that would be required for a
complete lifecycle?

Good question, glad I asked it :)

As Bonnie points out, there are many methodologies. As an interviewer, I would like to hear you speak as if you have actually used one or more of the models out there.

Let me get to the answer in a few minutes. First of all, where do you go to research this question?

www.rational.com has quite a bit of information on their Rational Unified Process. www.starbase.com (now part of Borland) has information on their requirements-based methodology. Both are good sources of information.

www.stickyminds.com is the official website of the STQE (software testing and quality engineering, I believe). They have a massive amount of information, some of which is free.

"Software Requirements" by Karl Weigers is my Bible to the process.

That said, the answer I would give:

Any living entity has a lifecycle: birth, developmental period (childhood), maintenance (adult), and death.

To fully document a software lifecycle, I would use the following:

1. Vision and Scope document, which answers the question, "Why do we need a new system?"

2. Validation Plan, which answers the questions, "What process will we follow? How will we know when the system is finished? What will we do when it dies?"

3. Functional Requirements Specification, which answers the question, "What is this system supposed to do?" from the user's standpoint.

4. System Development Specification, which answers the question, "How should the system be built?" from the developer's standpoint.

5. Test Plan, created from the FRS, which answers the question, "How will we know if the system works correctly?"

6. Qualification Document, showing the results of the tests and signed off by stakeholders.

7. User Documents, showing a user how to operate the system.

8. Change Requests, which track any changes to the finished system.

9. When the system is no longer needed, a document should be permanently filed which explains why the system is no longer needed and what should be done with any of the left-over data. (Anybody out there have a 5-1/4" disk in their filing cabinet?)

Diane Evans
Technical Writer

Washington State Coordinator, Tombstone Project
http://www.rootsweb.com/~cemetery/washing.html




_________________________________________________________________
Help STOP SPAM: Try the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.

Order RoboHelp X3 today and receive a $100 mail in rebate and a FREE
WebHelp Merge Module for merging multiple Help systems on any desktop
or server. Order online today at http://www.ehelp.com/techwr-l

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.



Previous by Author: Re: Preparation for a phone screen interview
Next by Author: RE: Preparation for a phone screen interview
Previous by Thread: RE: Preparation for a phone screen interview
Next by Thread: Re: Preparation for a phone screen interview


What this post helpful? Share it with friends and colleagues:


Sponsored Ads