Management: Work Package Plan

Software Agreement

 

 

1.      Richard Wolff is assigned the responsibility for performing the job function of GNIRS Software Engineer.

a)      This implies that he is a member of the GNIRS instrument team, accountable to the PM and PS for progress and budget on all software tasks, attending weekly project meetings, design reviews, and speaking as the responsible individual for all software related tasks for the GNIRS project.

b)      Richard will operate with maximum autonomy, as do the other engineers assigned to the project.

c)      Any individuals working with Richard on the software task would receive their direction only from him, and Richard is accountable for the work performed by them.

d)      Richard is to review and revise the overall software task which has the following budgets and schedule:

-  Total budget:            4550 hrs

-Software         4112 hrs

- Manuals             438 hrs

-         Low level code for integration by July 2, 2001

-         Operating software by December 2001

-         Complete software task by June 2002

  Note: the schedule dates are not negotiable to any significant degree.  These dates are driven by hardware assembly and test schedules, and the software cannot be allowed to cause slippage in these dates without direct impact on delivery in July 2002.

  2.      As the GNIRS Software Engineer Richard is responsible for:

a)      All tasks relating to delivering operating software

b)      Supervising any software programmers or engineers who might be assisting him in these tasks.

c)      Becoming familiar with the GNIRS instrument design and functions/modes of operation.

d)      Determining high and low level software requirements

-         this implies examining Gemini ICD’s and working with Jay Elias (Systems Engineer) in finalizing requirements for both levels of the software

-         holding/conducting appropriate reviews of the software requirements and design to insure compatibility with the instrument design

e)      Providing low level software to the instrument team for use in integration and test.  This software would be a deliverable to the team by July 2, 2001.

-         a hardware simulation tool will be provided for use in checkout of this software

-         the software would be completely checked out using the instrument electronics and simulation tool prior to the need date

f)        Providing the final operating software by December 2001.

-         this software would be used in GNIRS final testing, which includes cold testing and acceptance testing

-         December 2001 is the first opportunity available to test the operating software.  The final software needs to be complete and available by June 2002, in time for acceptance testing.

g)      Writing the Software Maintenance Manual and contributing to the User’s Manual.

-         both manuals have a draft and final revision phases

 

 

 

____________________                                ____________________            

Neil Gaughan                                                    Richard Wolff                              

Project Manager                                               Software Manager

GNIRS                                                            GNIRS

If you have any questions or suggestions regarding this website, please contact Melissa Bowersock.

---

NOAO Intranet Services

NOAO Copyright  Statement

National Optical Astronomy Observatories, 950 North Cherry Avenue, P.O. Box 26732, Tucson, Arizona 85726,
Phone: (520) 318-8000, Fax: (520) 318-8360