Supporting Information Document (SID)

Supporting Information Document (SID)Version 2.0

Supporting Information Document (SID)

The Log Angeles Community Garden Inventory and Locator

Team 13

Ardalan YousefiProject Manager

Cole CecilIntegrated Independent Verification & Validation

Jeff TonkovichImplementer

Shi-Xuan Zeng (Gary)Tester

02/05/12

Version History

Date / Author / Version / Changes made / Rationale
10/03/11 / Larry / 0.1 /

Added basic definitions to some of the commonly used words for the project

Make sure everyone is using the right words

10/04/11 / Larry / 0.2 /

Switched the traceability matrix table from NDI/NCS to architecture agile

Confirmed with TA that the process for this project is architecture agile, not NDI/NCS

10/06/11 / Larry / 0.3 /

Added and modified some word definitions in the glossary and started to fill out the matrix from SSRD

Synchronized with other documents on the vocabulary

10/07/11 / Larry / 0.4 /

Tracing from SSAD/use cases to the matrix

SSAD is provided by other team members

10/10/11 / Larry / 0.5 /

Changed to the status of the SID to reflex its status and the versions that are being produced by other members

Make SID up-to-date

10/12/11 / Larry / 0.6 /

Updated the traceability matrix to make LOS-2 to LOS-1,

SSRD was updated to remove LOS-1.

10/13/11 / Larry / 0.7 /

Adding location/URL for the documents, and adding some ICSM/577 related word descriptions

Core FC package remarks from TAs.

10/14/11 / Larry / 0.8 /

Updating the document versions and links, added traceability matrix entries for new OC numbers. Changed OCD’s LOS-2 to LOS-1 because LOS-1 was deleted from OCD.

Sync with final versions submitted for draft FC package.

10/16/11 / Larry / 0.9 /

Updated Traceability Matrix

SSRD requirements changed and removed.

10/17/11 / Larry / 0.10 /

Updated Traceability Matrix

Tracing bugs found by IIV&Ver.

10/20/11 / Larry / 0.11 /

Updated document versions and links

Pre-ARB updates

10/24/11 / Larry / 1.0 /

Updated Traceability Matrix
Move major version up

New artifacts from SSAD document and for official FC package

11/08/11 / Larry / 1.1 /

Moved the document to draft FC phase.

11/09/11 / Larry / 1.2 /

Updated Traceability Matrix

New Win conditions added to SSRD document CRs.

11/16/11 / Larry / 1.3 /

Updated Traceability Matrix with ATPC test plan and test cases numbers.

Draft ATPC test plan and test cases are identified.

11/21/11 / Larry / 1.4 /

Updated file versions for the documents

Submission for the draft FC package

11/28/11 / Larry / 1.5 /

Updated file versions

IIVVer feedback

12/02/11 / Larry / 1.6 /

Updated file versions for the files
Corrected traceability matrix for CR-8 and CR-21 since the split into two capability requirements
Added new use cases from SSAD to traceability matrix.

Submission for the official FC package

12/05/11 / Larry / 1.7 /

Updated file versions

Last update before submission for the DC package

01/25/12 / Ardalan / 1.8 /

Corrected the version of FED

IIVV feedback

02/05/12 / Jeff / 2.0 /

Updated Glossary
Updated files versions
Updated Section 4

Added missing definitions
QMP had new section added

Supporting Information Document (SID)

Version History

Table of Contents

Table of Tables

Table of Figures

1.Introduction

1.1Purpose of the SID Document

1.2Status of the package

1.3References

2.Traceability Matrix

3.Glossary

4.Document Tailoring

SID_RDCP_S12b_T13_V2.0.doc1Version Date:02/05/12

Supporting Information Document (SID)Table of Contents

Table of Tables

Table 1: Traceability Matrix for Architected Agile Team

SID_RDCP_S12b_T13_V2.0.doc1Version Date:02/05/12

Supporting Information Document (SID)Table of Contents

Table of Figures

No table of figures entries found.

SID_RDCP_S12b_T13_V2.0.doc1Version Date:02/05/12

Supporting Information Document (SID)Version 2.0

1.Introduction

1.1Purpose of the SID Document

The purpose of the Supporting Information Document (SID) is to reference between the corresponding Win requirements/agreements from the WinWin Negotiation activities to other documents such as Operational Concept Document (OCD) to ensure the requirements/agreements are documented and implemented in those documents.

The SID is also to indicate the versions of documents that are submitted with each commitment package as not to confuse incremental versions of the documents with the final versions of the documents that are submitted.

1.2Status of the package

The SID has compiled a list of commonly used words or definitions used in the scope of the project. Traceability Matrix is constructed between OCD, SSRD, SSAD, and ATPC. The tailoring of the SSAD and IP documents are also recorded. All documents and the final versions for the draft RDC package are also listed. This version is the first version in the Rebaselined Foundations phase.

1.3References

This version of SID is for the draft RDC package, and the following final documents are submitted together:

Operational Concept Description (OCD) Version 4.0

Prototype Report (PRO) Version 3.0

System and Software Requirements Definition (SSRD) Version 2.0

System and Software Architecture Description (SSAD) Version 2.0

Life Cycle Plan (LCP) Version 3.0

Feasibility Evidence Description (FED) Version 4.0

Supporting Information Document (SID) Version 2.0

Quality Management Plan (QMP) Version 2.0

Iteration Plan (IP) Version 1.0

Transition Plan (TP) Version 1.0

Acceptance Plan and Test Cases (ATPC) Version 1.0

Testing Procedures and Results (TPR) Version 1.0

2.Traceability Matrix

Table 1: Traceability Matrix for Architected Agile Team

OCD / Win Agreement / SSRD / SSAD / Test Case
WC_1145 / PR – 3
WC_1126 / CR – 24, 25
WC_1093 / CR – 23
WC_1092 / CR – 22, 26, 27, 28
WC_1038 / SR – 1
WC_967 / CR – 15 / ATF – 4
UC – 12 / TC-02-05
OC – 1 / WC_12 / CR – 2, 17, 18, 19, 20 / ATF – 2
UC – 3, 4, 5
OC – 1 / WC_13 / CR – 18, 29 / ATF – 2
UC – 3, 4 / TC-07-01
OC – 1 / WC_16 / CR – 17, 18, 19, 20 / ATF – 2
UC – 5 / TC-07-02
TC-07-03
OC – 2 / WC_8 / CR – 1, 3, 4 / ATF – 3, 4, 5
UC – 1, 2
OC – 2 / WC_9 / CR – 3, 4, 5 / ATF – 2, 3, 4, 5
UC – 1, 2 / TC-01-01
TC-01-02
TC-01-03
TC-01-04
TC-01-05
OC – 2 / WC_10 / CR – 9 / ATF – 2
UC – 6 / TC-04-01
TC-04-02
OC – 2 / WC_15 / CR – 8 / ATF – 1, 2
UC – 9 / TC-06-01
TC-06-02
OC – 2 / WC_25 / CR – 12, 13 / UC – 14, 15 / TC-03-01
TC-03-02
TC-03-03
TC-03-04
OC – 2 / WC_33 / CR – 8 / ATF – 1, 2
UC – 9 / TC-06-01
TC-06-02
OC – 2 / WC_37 / CR – 8 / ATF – 1, 2
UC – 9 / TC-06-01
TC-06-02
OC – 2 / WC_38 / CR – 9, 10, 11 / ATF – 2
UC – 6, 7 / TC-04-01
TC-04-02
TC-04-03
TC-04-04
TC-04-05
OC – 2 / WC_49 / CR – 3, 4 / ATF – 4, 5
UC – 1, 2 / TC-01-01
TC-01-02
TC-01-03
TC-01-04
TC-01-05
OC – 2 / WC_52 / CR – 9, 10 / ATF – 2
UC – 6 / TC-04-01
TC-04-02
OC – 2 / WC_325 / CR – 21
SR – 2 / ATF – 1, 2
UC – 9, 13 / TC-08-01
OC – 2 / WC_327 / CR – 6 / ATF – 2 / TC-05-01
OC – 2 / WC_328 / CR – 7 / ATF – 2 / TC-05-02
OC – 3 / WC_723 / CR – 14, 15, 16 / ATF – 3, 4, 5
UC – 10, 11, 12 / TC-02-01
TC-02-02
TC-02-03a
TC-02-03b
TC-02-04
TC-02-05
TC-02-06
OC – 4 / WC_11 / CR – 21 / ATF – 1, 2 / TC-07-02
TC-07-03
TC-07-05
TC-08-01
OC – 4 / WC_15 / CR – 8 / ATF – 1, 2
UC – 9 / TC-06-01
TC-06-02
OC – 5 / WC_16 / CR – 17, 20 / ATF – 2
UC – 4, 5 / TC-07-02
TC-07-03
OC – 6 / WC_8 / CR – 3, 4 / ATF – 3, 4, 5
UC – 1, 2
OC – 6 / WC_9 / CR – 3, 4 / ATF – 3, 4, 5
UC – 1, 2 / TC-01-01
TC-01-02
TC-01-03
TC-01-04
TC-01-05
OC – 7 / WC_328 / CR – 7 / ATF – 2 / TC-05-02
LOS – 1 / WC_47 / LOS – 1

3.Glossary

LANLT

Los Angeles Neighborhood Land Trust

LACGC

Los Angeles Community Garden Council

UCCE

University of California Cooperative Extension

LACC

Los Angeles Conservation Corp

Garden

Refers to the community gardens for the propose of this project

Database Manager

The users responsible for adding/editing/deleting garden records from the database, as well as generating reports and exporting them when necessary

Administrator

The one and only user account that is responsible for managing user accounts for the database managers, such as creating and deleting user accounts, or changing user account passwords

External delivery component

The part of website that the general public/everyone can access for garden information and the associated mapping tool

Internal database component

The part of website that is protected with secure login to allow only the database managers access to the database and the specific functionalities

Mapping Tool

The Google Map functionality that indicates the locations of the gardens on the map, according to the gardens’ longitude and latitude coordinates

User

The people who has access and uses the internal database component part of the website to manage garden information database, can be either Database Manager or Administrator

End-user

The people who only have access to the external delivery component part of the website to view garden information in limited details

Operational Concept Description. [Taken from ICSM EPG] This artifact represents the description for the new proposed operational concept to the success-critical stakeholders' (also known as “key stakeholders”) shared vision of the project being undertaken.

Prototype Report. [Taken from ICSM EPG] This artifact records information about various versions of prototypes, screenshots, and system navigation flows.

SSRD

System and Software Requirements Description. [Taken from ICSM EPG] The purpose of this artifact is to enumerate and explain the various requirements that follow from (elaborate upon) the results of the WinWin negotiations among key stakeholders.

SSAD

System and Software Architecture Description. [Taken from ICSM EPG] The purpose of the this artifact is to document the results of the object-oriented analysis and design (OOA&D) of the system being developed.

Feasibility Evidence Description. [Taken from ICSM EPG] This artifact reports the evidence of project feasibility in term on business case analysis, risk assessment, and etc.

Supporting Information Document. [Taken from ICSM EPG] The current artifact. Please refer to section 1.1 for the purpose of the artifact.

ICSM

Incremental Commitment Spiral Model. [Taken from ICSM EPG] ICSM is a Software Engineering (SE) process model that is used for the purpose of the project. It is an iteration process model with phases and milestones, and is risk-based.

Milestone

A milestone is an end of a ICSM iteration phase where critical-success stakeholders get together to go over and review the progress of current iteration phase before deciding whether to proceed to the next phase, repeat the current phase, or even discontinue the project based on the risks.

WinWin Negotiation

[Taken from ICSM EPG] This is a negotiation model where the success-critical stakeholders use to iterate through project expectations, requirements, and features to create win conditions, then finally negotiate and agree to commit on the win conditions.

Valuation Commitment Package. The list of artifacts that are submitted for the milestone at the end of Exploration Phase of ICSM model.

Foundations Commitment Package. The list of artifacts that are submitted for the milestone at the end of Valuation Phase of ICSM model.

Development Commitment Package. The list of artifacts that are submitted for the milestone at the end of Foundations Phase of ICSM model.

RDCP

Rebaselined Development Commitment Package. The list of artifacts that are submitted for the milestone at the end of Foundations Phase of ICSM model.

ATPC

Acceptance Test Plan and Cases. [Taken from ICSM EPG] This artifact’s purpose is to describe the scope, approach, resources and schedule of testing activities.

ATPR

Development Commitment Package. [Taken from ICSM EPG] This artifact details the activities required to prepare for and conduct specific system tests and to document their results. Preparatory activities include delegating to all responsible parties the tasks which they are to perform and the schedule to be following in performing said tasks.

Iteration Assessment Report. [Taken from ICSM EPG] This artifact records the assessment result provided by the Client at the end of each iteration.

Support Plan. [Taken from ICSM EPG] This artifact records the strategy, resources and responsibilities of system-support related activities.

Regression Test Package. [Taken from ICSM EPG] This artifact’s purpose is to provide the necessary test cases required to test changes made after project delivery to ensure that no existing functionality is broken by new features or changes.

Training Plan. [Taken from ICSM EPG] This artifact’s purpose is to lay out the plan for training-related activities.

User Manual. [Taken from ICSM EPG] This artifact teaches and guides the user on how to use the product, i.e. the steps for running the software, describes the expected output(s), and describes measures to be taken if errors occur.

Release Description. [Taken from ICSM EPG] This artifact describes items, particularly executables that will be made available to client and users after the completion of a development incremental plan.

4.Document Tailoring

Section 3 Technology Independent Design for the SSAD document has been removed as TA mentioned in class that for the scope of CS577 and the time constraints, the project does not need a technology independent design; instead a technology dependent design is all that is needed.
Section 1 Iteration Overview for the IP document has been modified to add another level to accommodate information for multiple iterations. Each iteration has its own subsection then Capabilities to be Implemented/Tested/not to be Tested sections underneath instead.
Section 3.4.1 SVN Guidelines has been added to the QMP document to which describes how to use SVN within the scope of CS577b.

SID_RDCP_S12b_T13_V2.0.doc1Version Date:02/05/12