The Elsmar Cove Forum and Site Map The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page

Go Back   The Elsmar Cove Forum > Common Quality Assurance Processes and Tools > Software Quality Assurance


The Elsmar Cove Forum SideBar!
Monitor the Forum
Monitor New Forum Posts
New Threads Feeds
RSS FeedRSS Feed
Sponsor Link










$ Contributor Forum Access
Courtesy Quick Links

Links that Elsmar Cove visitors will find useful in your quest for knowledge:


Howard's International Quality Services

Atul's Symphony Technologies

Dave Scott's Scott Quality Solutions

Praxiom Research Group


NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest Portal

IEST - Institute of Environmental Sciences and Technology

ASQ - American Society for Quality


All the Important Standards and Related Web Sites in the World
Reply
 
Thread Tools Search this Thread Rate Thread Content Display Modes
  #1  
Old 29th October 2006, 09:36 PM
HPLJJ HPLJJ is offline
Inactive Registered Visitor

Registration Date: Oct 2006
Location: Australia
 
Posts: 3
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 13
HPLJJ has disabled his/her Karma.
Question IT Software Life Cycle Development - How do 7.3.2 to 7.3.4 apply?

I'm new to this fantastic forum and have done some searching but couldn't find any reference to my problem - so, sorry if it has been covered before.

My company develops IT software. We have a fairly standard development life-cycle with design and development phases being as follows:
1. requirements design/document and review,
2. software design/document and review, and
3. code development and review

I am unsure as to how these equate to the clauses 7.3.2 (input), 7.3.3 (outputs) and 7.3.4 (review) as all 3 have inputs, outputs and reviews.

Jane
Reply With Quote

Sponsored Links
  #2  
Old 29th October 2006, 10:21 PM
Sidney Vianna's Avatar
Sidney Vianna Sidney Vianna is offline
Post responsibly

Registration Date: Oct 2001
Location: Long Beach, CA - USofA
 
Posts: 4,951
Thanks Given to Others: 688
Thanked 1,912 Times in 1,083 Posts
Karma Power: 467
Karma: 16797
Sidney Vianna is appreciated, and has over 1700 Karma points.
Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.Sidney Vianna is appreciated, and has over 1700 Karma points.
Default Re: IT Software Life Cycle Development - How do 7.3.2 to 7.3.4 apply?

Quote:
Originally Posted by HPLJJ View Post

I'm new to this fantastic forum and have done some searching but couldn't find any reference to my problem - so, sorry if it has been covered before.

My company develops IT software. We have a fairly standard development life-cycle with design and development phases being as follows:
1. requirements design/document and review,
2. software design/document and review, and
3. code development and review

I am unsure as to how these equate to the clauses 7.3.2 (input), 7.3.3 (outputs) and 7.3.4 (review) as all 3 have inputs, outputs and reviews.

Jane
Those would be phases of the product development. Phase 1 output will be part of phase 2 input and so on and so forth. Suggest you get a copy of ISO/IEC 90003 Guidelines to the application of ISO 9001 to computer software.
__________________
Fighting organizational dysfunction, one post at a time.
Reply With Quote
Sponsored Links

  #3  
Old 29th October 2006, 10:28 PM
harry harry is offline
Super Moderator

Registration Date: Sep 2005
Location: Johore/Malaysia
 
Posts: 2,946
Thanks Given to Others: 572
Thanked 1,031 Times in 746 Posts
Blog Entries: 1
Karma Power: 231
Karma: 7783
harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.
harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.
Default Re: IT Software Life Cycle Development - How do 7.3.2 to 7.3.4 apply?

Would the following, extracted from ISO IEC 90003 be of help to you?

7.3.2 Define software design and development inputs.

* Specify product design and development inputs.

* Record product design and development input definitions

* Evaluate product design and development input definitions.

* Review input definitions before you approve them.

* Derive software design and development inputs.

* Derive software design and development
inputs from functional requirements.

* Derive software design and development
inputs from performance requirements.

* Derive software design and development
inputs from quality requirements.

* Derive software design and development
inputs from safety requirements.

* Derive software design and development
inputs from security requirements.


7.3.3 Generate software design and development outputs.

* Create software product design and development outputs.

* Approve software design and development outputs prior to release.

* Use design and development outputs to control software product quality. *
* Maintain a record of your software design and development outputs.


7.3.4 Carry out software design and development reviews.

* Carry out reviews throughout your software
product design and development process.

* Establish procedures that specify how problems identified during
your software design and development reviews should be handled.

* Establish procedures that specify how product
deficiencies or nonconformities should be handled.

* Establish procedures that specify how process
deficiencies or nonconformities should be handled.

* Formulate the guidelines that all participants will be expected
to follow during your software design and development reviews.


Regards.

Last edited by harry; 29th October 2006 at 10:34 PM.
Reply With Quote
  #4  
Old 29th October 2006, 10:29 PM
HPLJJ HPLJJ is offline
Inactive Registered Visitor

Registration Date: Oct 2006
Location: Australia
 
Posts: 3
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 13
HPLJJ has disabled his/her Karma.
Default Re: IT Software Life Cycle Development - How do 7.3.2 to 7.3.4 apply?

I agree with what you are saying re Phase 1 output will be part of phase 2 input etc.

I am trying to map our development/build process to the ISO 9001 clauses under 7.3 Design and Development considering it is a phased process.
Reply With Quote
  #5  
Old 29th October 2006, 10:37 PM
HPLJJ HPLJJ is offline
Inactive Registered Visitor

Registration Date: Oct 2006
Location: Australia
 
Posts: 3
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 13
HPLJJ has disabled his/her Karma.
Default Re: IT Software Life Cycle Development - How do 7.3.2 to 7.3.4 apply?

I have an extract of the iso/iec 90003 for these clauses but I still have my question.

Does clause 7.3.2 cover our Inputs for
- Requirements phase
- Software Design phase, and
- Coding

and the same for 7.3.3 and 7.3.4 because they all have inputs, outputs and reviews

tks,
Jane
Reply With Quote
  #6  
Old 29th October 2006, 10:55 PM
harry harry is offline
Super Moderator

Registration Date: Sep 2005
Location: Johore/Malaysia
 
Posts: 2,946
Thanks Given to Others: 572
Thanked 1,031 Times in 746 Posts
Blog Entries: 1
Karma Power: 231
Karma: 7783
harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.
harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.harry is appreciated, and has over 1700 Karma points.
Default Re: IT Software Life Cycle Development - How do 7.3.2 to 7.3.4 apply?

Reviews are basically improvement process (and checks made to ensure all inputs and other requirements are taken care of) and whenever there are reviews/changes there will be new inputs and outputs. And they should be carried out at every stage of design and development.

Even at the 'beta' stage, there can be reviews (and therefore new input/output) as bugs etc are detected.

Regards.

Last edited by harry; 29th October 2006 at 11:25 PM. Reason: insert items in brackets
Reply With Quote
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Forum > Common Quality Assurance Processes and Tools > Software Quality Assurance

Bookmarks


Visitors Currently Viewing this Thread: 1 (0 Registered Visitors and 1 Unregistered Guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
Software Design SOP to ISO 62304 (Software life cycle for Medical Device) ISO 13485 - Medical IEC 62304 - Medical Device Software Life Cycle Processes 3 15th August 2009 09:56 AM
IEC 62304:2006 Medical device software - Software life cycle processes - Issued wrodnigg IEC 62304 - Medical Device Software Life Cycle Processes 10 23rd June 2009 11:35 AM
Life Cycle - ISO 12207 - Software development activities Marc Software Quality Assurance 4 24th March 2008 12:06 PM
Software Life Cycle - Software Development Procedure HellenK Software Quality Assurance 2 7th August 2006 03:19 PM
Comparison of Waterfall vs Life Cycle in Software Development Methods RosieA Software Quality Assurance 5 29th October 2003 09:02 AM



The time now is 01:02 PM. All times are GMT -4.
The time zone can be changed in your UserCP --> Options.



   

All Y'All Come Back Now, Y' Hear?

Made With A Mac! FreeBSD OS Powered by Apache!
Using php4 Forums provided and maintained by Marc Smith Database by MySQL

FAIR USE and CORRECTNESS NOTICE: This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe herein constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit to those who have expressed a prior interest in receiving the included information for research and educational purposes. For more information go to: http://www.law.cornell.edu/uscode/17/ If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. In addition, I do not guarantee the correctness of the content. The risk of using content from the Elsmar Cove web site and forums remains with the user/visitor.

Responsibility Statement: Each person is responsible for anything they post in the Elsmar Cove forum. Neither I, Marc Timothy Smith, nor any of the forum Moderators, are responsible for the content of posts people make. Liability for post content resides with the poster as does interpretation and/or acceptance and/or use of advice by the reader.

Complaints: If you have a complaint with a post in a forum discussion thread, including Content in general, fighting, flaming, copyright infringement, defamation and/or 'slander', please use the 'Report This Post Report This Post Button button which appears at the top of every post in every thread.

Site courtesy of:
Marc Timothy Smith - Cayman Business Systems, 8466 Lesourdsville-West Chester Road, West Chester, Ohio 45069-1929 - USA
(513) 341-6272

To contact me, click the Google Voice link below, enter Your Name and Your Phone Number and Google will ring your phone and connect you for free!

The Elsmar Cove Web Site is *CopyFree*
no new posts