Hello Ram,

Review can be treated as a Verification mechanism to ensure that work
products are as per the standards and meets all the required criteria.
Audits are needed to ensure that the inconsistencies in the review process /
work products were properly closed and the process/documents are properly
following the procedures. It is consistent with the adopted  workflow.
Audits are a validation mechanism.

regards
Sudheer

-----Original Message-----
From: RamanathanS [mailto:ramanathans@...]
Sent: Friday, January 31, 2003 11:46 AM
To: spi@yahoogroups.com
Cc: softwarequality@yahoogroups.com
Subject: [SPI] Work product audit VS Peer Review


Hello all

I would be greatful if someone can through some light on work product audits
and peer reviews.

when are these audit performed? what is being reviewed? what would be the
major differences between these two techniques?

Thanks in advance

Ram



Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via
spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com.
Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com.

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Hello Abrachan,

1. The life cycle model chosen for a project depends on a variety of factors
including complexity, size, clarity of requirements, etc.. Just that the
project is open source is too vague to suggest one.

2. The same is the case with project management. Is the team in one location
or distributed over the world? Is there a responsible person coordinating
the activities? If so what is the control he has over the team members?

3. What are the critical factors for your project? Is it schedule or is it
ensuring some functionality? Identify these and they could help you identify
the major risks.

4. There are a number of tools available for configuration management over
internet. CVS, Source off-site, etc. The problems are in identifying who is
responsible for what and when. Answers to these will be decided by the
project management.

5. Quality assurance (as distingushed from quality control), is a management
function. Functioning of QA depends a lot on the control the management has
over the project members.

These are just a few thoughts that came to my mind. I would be glad to get
more comments on these, any one?

Regards
Roy

-----Original Message-----
From: pabrachan <pabrachan@...> [mailto:pabrachan@...]
Sent: Thursday, January 30, 2003 6:14 PM
To: spi@yahoogroups.com
Subject: [SPI] Process for open source projects


Is there anyone who can help me out with the software development
lifecycle for open source projects. I will be interested to know the
following;

1) The software development lifecycle
2) Project management template for open source projects
3) Common risks in open source projects
4) Configuration management for open source projects
5) Quality assurance of open source projects

Thanking you in advance

P.Abrachan



Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via
spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com.
Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com.

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

We are still looking for few more good proposals, especially in agile
approaches to software development and testing.
===========================================================================
If you do not wish to receive information about our educational programs,
reply with "Remove" in the subject line.  Please make sure that your message
contains The address that needs to be removed; not an alias or a forwarding
address.
=============================================================================

Call for Papers and Presentations

The International Conference on
Practical Software Quality Techniques
PSQT 2003 East

The International Conference on
Practical Software Testing Techniques
PSTT 2003 East

June 9 - 13, 2003, Washington D.C. Area


Proposals for papers and/or presentations reflecting real experiences with
practical software quality techniques or practical software testing techniques
are invited for both conferences.   We would like to hear from you if you have
expertise or experiences in any software quality, testing technique, or tool. 
This is a great opportunity to share your experience with other software
professionals and get their feedback in this practice-oriented conference. 
Topics of interest include:

* Testing Technology, Testing Process and Test Automation
* Inspections, Reviews, and Walkthroughs
* Software Process Assessment and Improvement
* Web and e-Commerce Related Quality and Testing Issues
* Quality Management Issues
* Measurements and Benchmarking
* ISO 9000 Certification
* Configuration Management and Version Control
* Change Tracking
* Project Management
* Risk Assessment
* Requirement Management
* Automated Tools Dealing with any of these areas.
Proposals dealing with other topics will also be considered.

Important dates:
February 17, 2003: Proposals for papers and presentations are due
March 3, 2003:  Notification of acceptance/rejection will be mailed out
April 28, 2003: Copies of presentations and papers are due

The acceptance of a proposal does NOT guarantee acceptance of the presentation
or paper.  Presentations and papers must address all issues proposed in the
proposal to be accepted.

All accepted papers and presentations are awarded a free admission to the
PSQT/PSTT 2003 EAST two-day conference where they are presented and a copy of
the conference proceedings.  In addition, the best paper or presentation as
judged by the conference delegates will be invited as a featured presentation in
the following conference.

Submissions:

All submissions must be sent via e-mail to the Program Chair, Jamie Mitchell at
jmitchell@... as follows:

        One file in MS Word or RTF format containing all items under submission
rules below
        One file in MS Word or RTF format containing the paper if available
        One file in PowerPoint containing the presentation if available

Do not include any part of your submission in the body of the message.

Submission Rules:

(Any submission that does not follow exactly these rules will not be considered
by the program committee)

Proposals must include ALL items below:
1. Presentation title
2. Indicate whether the proposal is for a presentation only or for a paper and a
presentation.  Papers are not accepted unless they will be presented.
3. Presenter's name, title, company/organization name
4. Mailing address, telephone number, fax number, and E-mail address
5. Detailed biography indicating specific experiences with the subject of the
presentation.
6. A narrative description of the concepts covered by the presentation
7. A detailed outline of the presentation.  This outline is needed for inclusion
in the conference proceedings and the web site.   Submitting the actual
presentation slides or a paper as in item 10 or converting power point
presentation to outline DOES NOT substitute for the item.
8. Five to six bullets corresponding to the learning objectives of the
presentation
9. Indicate whether the material was presented before and name and date of the
event.
10. If presentation slides or a paper on the topic is available attach a copy. 
This will provide more information to the selection process.

Proposals and presentations must meet the following guidelines
1. Do not include any company specific terms or acronyms unless defined
2. Must focus on what can be learned
3. Must not propose any introductory or text-book type material
4. The focus must be on specific experiences rather than vague advice
5. Must not promote any service or products

I need some help for SCM activities in a small "maintenance" project.
I [PM] use VSS for my project documents and source code. The folder
structure is as follows:
[1] Documents => Only PM has full access, Team members [TMs] have
READ access.
[2] Source => PM and TMs have full access. I have given full access
to TMs because they need to check-in/out the code for modifications.

The question now is ... is one folder sufficient for source?
Currently whenever there is a change request, affected source files
are checked out by TMs. Once the coding is complete, they check-in
and label each one of them as "ToBeReviewed". I do the review. I am
not sure how to proceed further with VSS labels, becuase if there are
any findings in code review, they need to be closed and check-
in/check-out loop will continue till all points are closed. Finally
when everything is ready for release, the executable is built and the
source folder is labeled with a suitable version say 1.1 etc.

Pls help me in this regard.

Dear all,

my co is deciding on the vendor for CMMI services.
Iflex and KPMG have been shortlisted.

Let me know if you are aware of any companies in India
that have taken Iflex's services on CMMI

Regards

=====
     [input]    [input]

__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com

Hi Qaiser,

I logged in after a long time and found your message and just had to
reply to this one. Yes, I am also doing a lot of analysis on defects
as i am implementing Defect Prevention in my organization. here's
what i'm doing (this is going to be long):

You would need just a few details on defects and then you can do a
million things with the data. you would need the type of defect
(functionality/GUI/Coding Standards/incorrect data and so on...), the
severity of defects (major/minor/critical etc) and reason for defect
(ignorance/missing standards etc)...along with the usual when raised,
stage of injection and detection and when fixed and by whom etc...


you can do a few of the following things with this now:
1. find out Defect type and do a pareto and causal analysis and
remove the common types of defects followign an action plan for
defect removal and prevention. this will improve your project's
performance considerably.
2. Review efficiency: Find out how many defects get caught at the
review stage and at testing stages and also in which testing cycle
(this will tell you how efficiently are you carrying out reviews and
testing. this will help improve the project's review performance).
3. find out how many defects do you get in acceptance and system
testing internally and how many are client re[ported post delivery.
if this number is high, you must take drastic measures with the
development and testing teams to improve performance.

you can use the SPC tools like Histograms (at organization level) and
control charts at project level to improve the performance
continuously. don't use too many complex tools as these will put off
people and will scare the life out of them! further you'd have to do
the initial analysis and then hand it over to the projects after some
training to ensure compliance. define baseline of performance and
then first control and then improve on it using this data that you
are collecting in the projects.

these are things that can be done to start with. i hope this helped
and if you or anyone in the group can add to my knowledge i'd very
much appreciate it.

Regards,
Sarika.



--- In spi@yahoogroups.com, "qaiser99pk <qaiser99pk@y...>"
<qaiser99pk@y...> wrote:
> Hi All,
> I am trying to do some thing in Bugs data analysis.Actually we have
> bugs database, but no one is using this database for project
> analysis. If some one have done some work in this field ,please let
> me know. I would also like to know that how can we use this
analysis
> to improve and track the performance of project.That is, how
project
> is going on and what type of action needed to be taken to overcome
> these problems.
>
> Thanks in Advance.
>
> Regards,
> Qaiser

Me too!! please do share your experiences with us! i've read some
about it and as far as my knowledge goes it requires a lot of
convincing with the customer!! Please share your experiences and help
us know more on the ractical implications of the methodology!

regards,
Sarika.



--- In spi@yahoogroups.com, "tom_cagley <tcagley@k...>"
<tcagley@k...> wrote:
> I recently worked on a project using an agile methods (eXtreme) in
> an organization last leverages CMMI.  I would like to contact
others
> that have had similar experiences (interview by phone or email) for
> a paper I am writing.

Hello all,

What are the most widely used/accepted standards for using symbols in
flowcharts?
Can you please share it with me?

Thanks,
Mayank D Goel

Only KPA you will not be able to handle properly without a tool support is
COnfiguration Management.  All others do not require any specific tool.

Regards,
Orhan
www.nitelik.net
www.kalayci.com


----- Original Message -----
From: <spi@yahoogroups.com>
To: <spi@yahoogroups.com>
Sent: Friday, February 07, 2003 9:09 PM
Subject: [SPI] Digest Number 634


>
> Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via
spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com.
Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com.
> ------------------------------------------------------------------------
>
> There is 1 message in this issue.
>
> Topics in this digest:
>
>       1. Req. for Tools/ Softwares List
>            From: rajendra prasad <rpgm@...>
>
>
> ________________________________________________________________________
> ________________________________________________________________________
>
> Message: 1
>    Date: Wed, 5 Feb 2003 20:44:35 -0800 (PST)
>    From: rajendra prasad <rpgm@...>
> Subject: Req. for Tools/ Softwares List
>
>
> Dear Friends - Seasonal Greetings to all.
>
> We have just initiated CMM activity and would like to know that what are
all the Tools and software's required for the same.
>
> Thanks in advance. RP
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now
>
> [This message contained attachments]
>
>
>
> ________________________________________________________________________
> ________________________________________________________________________
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>

I feel u can follow the below process:

Assumption as per ur mail: PM and TM both have full access to sourcecode.

1. TM checkout the files for modification and checkin the files
2.Dont label the checkin version
3. Take the latest file and review the code(PM), and give the comments to
update.
4.Checkout the file to modify for review comments.
5.Checkin the modified files based on review comments.
6. if so any other modification require continue the above process
7. else if no more correction or modification is required for the source
code then label the version.

Since the label to made only for the last version for the source code.
This I think it will solve ur problem.

Note: If u want to review the source code for particular version, then u can
right click and go to show history where it list all the version along with
user who has done checkin for that version.

Regards
Gajapathy P
----- Original Message -----
From: <gkmailid@...>
To: <spi@yahoogroups.com>
Sent: Wednesday, February 12, 2003 4:23 PM
Subject: [SPI] VSS labels and SCM


> I need some help for SCM activities in a small "maintenance" project.
> I [PM] use VSS for my project documents and source code. The folder
> structure is as follows:
> [1] Documents => Only PM has full access, Team members [TMs] have
> READ access.
> [2] Source => PM and TMs have full access. I have given full access
> to TMs because they need to check-in/out the code for modifications.
>
> The question now is ... is one folder sufficient for source?
> Currently whenever there is a change request, affected source files
> are checked out by TMs. Once the coding is complete, they check-in
> and label each one of them as "ToBeReviewed". I do the review. I am
> not sure how to proceed further with VSS labels, becuase if there are
> any findings in code review, they need to be closed and check-
> in/check-out loop will continue till all points are closed. Finally
> when everything is ready for release, the executable is built and the
> source folder is labeled with a suitable version say 1.1 etc.
>
> Pls help me in this regard.
>
>
>
>
>
> Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via
spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com.
Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com.
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>

FYI

See what Mark Paulk said about CMM and Agile:

http://groups.yahoo.com/group/spi/files/402c-S.pdf

 "sarika_shandilya <sarika_shandilya@...>" <sarika_shandilya@...> wrote:

Me too!! please do share your experiences with us! i've read some
about it and as far as my knowledge goes it requires a lot of
convincing with the customer!! Please share your experiences and help
us know more on the ractical implications of the methodology!

regards,
Sarika.



--- In spi@yahoogroups.com, "tom_cagley "
wrote:
> I recently worked on a project using an agile methods (eXtreme) in
> an organization last leverages CMMI. I would like to contact
others
> that have had similar experiences (interview by phone or email) for
> a paper I am writing.



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/FpY02D/vN2EAA/xGHJAA/nhFolB/TM
---------------------------------------------------------------------~->

Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com. Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com.

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Can anyone point me to a resource for reusing documents?  My documentation
requirements seem to be ballooning.  For each functional piece of software I
have:
  - Requirements docs for business process owners
  - High and low level designs for coding
  - Unit testing docs to prove coders tested the code
  - Regression testing docs for the regression testing team
  - Install docs for app support for each release.  These cover several
functional pieces per release.
  - App support manuals for troubleshooting problems and how to fix them

	 Now we have a new requirement.  We need a document to set up an
environment which may include several different functional pieces of
software (web servers, middleware, client code of different types).  This
covers some install instructions (slightly different for dev, test, QE and
prod) and  some explanation of what it does (but not much) and some tests
for when it's set up.

	 I need a good way to reuse some of the top documents to make the
bottom document easier to write and maintain.
	 The first one we wrote was a new document with cut and pasted parts
from the install docs on the top.  We factored out the environment specific
variables and put them in a table at the top of the document.
	 This was very time intensive.  Can someone suggest a better method?
I'm thinking that if we change the install documents on the top to look like
the install docs for the new requirement, we only have to write them once
per functional piece, but I'd like to know if there are any other
refinements before I start re-writing the working documentation to fit the
new requirement.
	 If this isn't clear, please let me know.
Thanks,
Joe

Joe Fair
"The beginning is the most important part of the work."
Plato, The Republic. Book II. 377B

Can anyone help me define the scope of Stage Gate in a company using SW-CMM or CMMI for SPI. I am well versed with CMM & I find the advantages offered by stage gate to be similar to that CMM promises.

Please help me clarify this concept.

Thanks & Regards

Kiran

 

Catch all the cricket action. Download Yahoo! Score tracker

Catch all the cricket action. Download Yahoo! Score tracker

Currently we carry out on-site projects' SQA reviews / SCM audits etc.
by asking concerned Project Leader to send requisite records at our HO
on monthly basis. The concerned SQA then reviews the project based on
the furnished records. Any clarification required by SQA is sought thru
e-mail or telehponic conversation.
Is there a better way or procedure for carrying out such reviews? If
anyone is ready to share his / her experience on the same?
Thanks

--
Satish Pendse
Godrej Infotech Limited,                      Tel: +91 22 55964020
Plant-19A, Second Floor,
Pirojshanagar, Vikhroli,                      Fax: +91 22 25181730
Mumbai 400079, INDIA
http://www.godrejinfotech.com/

Anyone knows any kind of directory of companies that could certify the level 2
or 3 in Europe?

How is possible to be a certifier company?

Thanks.

Anthony

Hi,

I really do not know at this time of heightened productivity
requirements why do we continue to use the old slow way of CM!!

I would say that the days of restricting access rights after creating
folders in VSS and CVS are gone! these are the days of parallel
development and we need not restrict any rights to anyone anymore!!

here is what i would suggest:

give access to everyone on the VSS. continue to label the code at
every logical break like review, testing and final release. the
labelling would automatically restrict any undersiable changes form
happening to your reviewed or tested code while also allowing the
developer to continue to develop other fiunctionalities in the same
piece of code!! so whenever you want the codeyou reviewed or tested
or want to release, just check out on the label and get all the files
for a particular label. and that would take care of anything and
everything. any time you want to do status accounting, you do it on
relevant labels only!

so what you are currently doing for review is right and just extend
this to other parts of lifecycle as well...but you need to make very
logical and strong naming conventions for the labels and files!! if
you don't follow it properly then you may possibly run into trouble
finding the right files but rarely...

please let me know if it helps at all!! i know it sounds different
but we should really come out of that folder control mode now!!

Regards,
Sarika.



--- In spi@yahoogroups.com, "Gajapathy" <gajapathy@k...> wrote:
> I feel u can follow the below process:
>
> Assumption as per ur mail: PM and TM both have full access to
sourcecode.
>
> 1. TM checkout the files for modification and checkin the files
> 2.Dont label the checkin version
> 3. Take the latest file and review the code(PM), and give the
comments to
> update.
> 4.Checkout the file to modify for review comments.
> 5.Checkin the modified files based on review comments.
> 6. if so any other modification require continue the above process
> 7. else if no more correction or modification is required for the
source
> code then label the version.
>
> Since the label to made only for the last version for the source
code.
> This I think it will solve ur problem.
>
> Note: If u want to review the source code for particular version,
then u can
> right click and go to show history where it list all the version
along with
> user who has done checkin for that version.
>
> Regards
> Gajapathy P
> ----- Original Message -----
> From: <gkmailid@y...>
> To: <spi@yahoogroups.com>
> Sent: Wednesday, February 12, 2003 4:23 PM
> Subject: [SPI] VSS labels and SCM
>
>
> > I need some help for SCM activities in a small "maintenance"
project.
> > I [PM] use VSS for my project documents and source code. The
folder
> > structure is as follows:
> > [1] Documents => Only PM has full access, Team members [TMs] have
> > READ access.
> > [2] Source => PM and TMs have full access. I have given full
access
> > to TMs because they need to check-in/out the code for
modifications.
> >
> > The question now is ... is one folder sufficient for source?
> > Currently whenever there is a change request, affected source
files
> > are checked out by TMs. Once the coding is complete, they check-in
> > and label each one of them as "ToBeReviewed". I do the review. I
am
> > not sure how to proceed further with VSS labels, becuase if there
are
> > any findings in code review, they need to be closed and check-
> > in/check-out loop will continue till all points are closed.
Finally
> > when everything is ready for release, the executable is built and
the
> > source folder is labeled with a suitable version say 1.1 etc.
> >
> > Pls help me in this regard.
> >
> >
> >
> >
> >
> > Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via
> spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com
> Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com
> >
> > Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
> >

We have guideline for PCA ( Physical Configuration Audit) and FCA ( Functional Configuration Audit), and related checklist. QA tailored the checklist specific to project and communicate with project based on the checklist for audit.

 sv pendse <svp@...> wrote:

Currently we carry out on-site projects' SQA reviews / SCM audits etc.
by asking concerned Project Leader to send requisite records at our HO
on monthly basis. The concerned SQA then reviews the project based on
the furnished records. Any clarification required by SQA is sought thru
e-mail or telehponic conversation.
Is there a better way or procedure for carrying out such reviews? If
anyone is ready to share his / her experience on the same?
Thanks

--
Satish Pendse
Godrej Infotech Limited, Tel: +91 22 55964020
Plant-19A, Second Floor,
Pirojshanagar, Vikhroli, Fax: +91 22 25181730
Mumbai 400079, INDIA
http://www.godrejinfotech.com/




------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/FpY02D/vN2EAA/xGHJAA/nhFolB/TM
---------------------------------------------------------------------~->

Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com. Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com.

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

        This article is pretty good.  Although it touches upon the problem of job titles (and their inflation), it does get into the details of the differences within the areas.  It also addresses the strong need for someone to be able to understand the customers requirements and translate them into software requirements.

        The full article can be found at:

                http://www.computerworld.com/developmenttopics/development/story/0,10801,78502,00.html?nas=APP-78502

MICHAEL S. BANDOR, MSgt, USAF
Software Quality Assurance Engineer
AFPC/DPDIQA
550 C Street West Suite 18
Randolph AFB, TX 78150-4720
DSN 665-2503/2121 Commercial: (210) 565-2503/2121
Email: michael.bandor@...
NOTE:  The information presented does not constitute an endorsement by the US Air Force, Department of Defense, or US Government.  It is provided for informational purposes only.

-----Original Message-----
From: sarika_shandilya <sarika_shandilya@...> [mailto:sarika_shandilya@...]
Sent: Friday, February 21, 2003 5:42 PM
To: spi@yahoogroups.com
Subject: [SPI] Re: VSS labels and SCM

Hi,

I really do not know at this time of heightened productivity
requirements why do we continue to use the old slow way of CM!!

I would say that the days of restricting access rights after creating
folders in VSS and CVS are gone! these are the days of parallel
development and we need not restrict any rights to anyone anymore!!

here is what i would suggest:

give access to everyone on the VSS. continue to label the code at
every logical break like review, testing and final release. the
labelling would automatically restrict any undersiable changes form
happening to your reviewed or tested code while also allowing the
developer to continue to develop other fiunctionalities in the same
piece of code!! so whenever you want the codeyou reviewed or tested
or want to release, just check out on the label and get all the files
for a particular label. and that would take care of anything and
everything. any time you want to do status accounting, you do it on
relevant labels only!

so what you are currently doing for review is right and just extend
this to other parts of lifecycle as well...but you need to make very
logical and strong naming conventions for the labels and files!! if
you don't follow it properly then you may possibly run into trouble
finding the right files but rarely...

please let me know if it helps at all!! i know it sounds different
but we should really come out of that folder control mode now!!

Regards,
Sarika.



--- In spi@yahoogroups.com, "Gajapathy" <gajapathy@k...> wrote:
> I feel u can follow the below process:
>
> Assumption as per ur mail: PM and TM both have full access to
sourcecode.
>
> 1. TM checkout the files for modification and checkin the files
> 2.Dont label the checkin version
> 3. Take the latest file and review the code(PM), and give the
comments to
> update.
> 4.Checkout the file to modify for review comments.
> 5.Checkin the modified files based on review comments.
> 6. if so any other modification require continue the above process
> 7. else if no more correction or modification is required for the
source
> code then label the version.
>
> Since the label to made only for the last version for the source
code.
> This I think it will solve ur problem.
>
> Note: If u want to review the source code for particular version,
then u can
> right click and go to show history where it list all the version
along with
> user who has done checkin for that version.
>
> Regards
> Gajapathy P
> ----- Original Message -----
> From: <gkmailid@y...>
> To: <spi@yahoogroups.com>
> Sent: Wednesday, February 12, 2003 4:23 PM
> Subject: [SPI] VSS labels and SCM
>
>
> > I need some help for SCM activities in a small "maintenance"
project.
> > I [PM] use VSS for my project documents and source code. The
folder
> > structure is as follows:
> > [1] Documents => Only PM has full access, Team members [TMs] have
> > READ access.
> > [2] Source => PM and TMs have full access. I have given full
access
> > to TMs because they need to check-in/out the code for
modifications.
> >
> > The question now is ... is one folder sufficient for source?
> > Currently whenever there is a change request, affected source
files
> > are checked out by TMs. Once the coding is complete, they check-in
> > and label each one of them as "ToBeReviewed". I do the review. I
am
> > not sure how to proceed further with VSS labels, becuase if there
are
> > any findings in code review, they need to be closed and check-
> > in/check-out loop will continue till all points are closed.
Finally
> > when everything is ready for release, the executable is built and
the
> > source folder is labeled with a suitable version say 1.1 etc.
> >
> > Pls help me in this regard.
> >
> >
> >
> >
> >
> > Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via
> spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com
> Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com
> >
> > Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
> >



Yahoo Group home: http://groups.yahoo.com/group/spi Subscribe via spi-subscribe@yahoogroups.com or to me at spi-owner@yahoogroups.com.  Unsubscribe by sending an email to spi-unsubscribe@yahoogroups.com.

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Could anyone please give me the difference between a 'deviation'
and 'tailoring' in SW CMM with an example from software development
lifecycle activities? Thanks in advance for your response.

                                           Regards,
                                                     Deepu

Hi

Tailoring  is a  "permissible deviation"  from the organization set
of standard processes to obtain a process that is suitable for the
specific needs of a project . The tailoring guideline will talk about
the allowed rules for tailoring that helps in optimizing the
organization processes and are not risk to the projects .  Tailoring
is essentially  addition, deletion or modification of actvities in a
process.

Deviations : These are over and above what is defined in the
tailoring guidelines . These are potential risks and needs to be
approved by the SEPG .

Hope this helps you


--- In spi@yahoogroups.com, "deepu30 <deepu@n...>" <deepu@n...> wrote:
> Could anyone please give me the difference between a 'deviation'
> and 'tailoring' in SW CMM with an example from software development
> lifecycle activities? Thanks in advance for your response.
>
>                                           Regards,
>                                                     Deepu

Hi Deepu,
Based on the type of projects, their life cycle activities change. For
example, in development kind of a project, you need to have very controlled
requirements management (RM) process, review and approval process etc
whereas in maintenance type of a project RM is very loose. So, your
organization process assets (QMS) can allow for tailoring of RM process.

But, there are some activities which need to be performed for all kinds of
projects, and so become mandatory activities in the project lifecycle. If
these activities are not be performed by any project, the project needs to
get "deviation" approved.

Hope this helps.

regards,
manoj.

>From: "deepu30 <deepu@...>" <deepu@...>
>Reply-To: spi@yahoogroups.com
>To: spi@yahoogroups.com
>Subject: [SPI] Deviation and Tailoring
>Date: Tue, 25 Feb 2003 13:08:39 -0000
>
>Could anyone please give me the difference between a 'deviation'
>and 'tailoring' in SW CMM with an example from software development
>lifecycle activities? Thanks in advance for your response.
>
>                                           Regards,
>                                                     Deepu
>
>


_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
http://join.msn.com/?page=features/virus

If you respond to this, please do so directly to the author and not to the SPI
group.

This questionnaire is a part of my software engineering project.
The responses will be only used in my project.2 minutes for you,but
many helps for me:)

Questions:

1,Where is your company?
A)USA
B)India
C)Europe
D)China
E)Others

2,How many software engineers are there in your company?
A)less than 100;
B)100 or more;

3)Has your company achieved ISO9000?
A)Yes
B)No

4)Which CMM level has your company achieved?
A)1
B)2;
C)3;
D)4;
E)5;
F)Not achieved

5)How long did it take your company to achieve CMM level2?
A)less than 1 year
B)1 year
C)between 1 and 2 years
D)2 or more than 2 years
E)Not in above list

6)What is the most important reason for your company implementing
CMM?
A)Improved software processes;
B)Get more contracts;
C)Others.Please specify______:


7)What do you think is most difficult in implementing CMM?
A)Documentation overload;
B)Limited resources;
C)Training costs;
D)Lack of guidance
E)Others. Please specify______:

8)Did your company use external consultant organizations?
A)Yes;
B)No;

9)Which KPAs of CMM level 2 has your company implemented?
A)Requirements Management;
B)Software Project Tracking and Oversight;
C)Software Subcontract Management;
D)Software Quality Assurance;
E)Software Configuration Management;
F)Project Planning;

10)In which order has your company implemented CMM level 2?
A)Requirements Management;
B)Software Project Tracking and Oversight;
C)Software Subcontract Management;
D)Software Quality Assurance;
E)Software Configuration Management;
F)Project Planning;
(For example:an answer is "AFBEDC")

Thank you very much!

Hi,

My name is Deepu. I am the single full-time SEPG guy in a
software development company that recently achieved ISO
certification. We have an intranet site where people can download
templates and read the organizational procedures. Now I need to set
up a Knowledge Management System/ Project Repository where the
various projects can display their Lessons Learned, Project Metrics,
documents they are proud of, etc. We are also considering a mailing
system which will enable project team members to get answers to
technical and project management queries also. Can anyone in this
group give me some guidelines or a framework to implement such a
system? If you can share some document or direct me to some website
where I can find information about implementing such a system, I
would be extremely thankful. Thanks in advance for your help.

Deepu
deepu@...

At 11:03 07/11/2002, you wrote:

>Can someone point me to a web page with those details?

Start at www.sysmod.com/psp.htm for information and many links

Hello all:

The Subcontract Management KPA covers the management
of a software subcontract, as well as the management
of the software component of a subcontract that
includes software, hardware, and possibly other
systems components. But, if you subcontract a
consulting service,
does it mean that this KPA is not applicable?

I would appreciate the answers from Lead Appraisers in
the group

Thanks a lot

Nuria

___________________________________________________
Yahoo! Móviles
Personaliza tu móvil con tu logo y melodía favorito
en http://moviles.yahoo.es

Re: deviation vs tailoring:

A client of mine has a mix of medium-sized development and small maintenance
projects.  Their project planning process requires all projects to create
software development plans.  The development projects use a full IEEE-format
SPMP, while the small maintenance projects use a two-page form-based project
plan template.  That's tailoring.

Not writing a plan at all would be a deviation.  If a development project tried
to get away with a 2-page project plan, that also would be a deviation.

--
Henrietta Foster
henrietta.foster@...