Create Access database for Project Management_v2

キャンセルされた 投稿 Jun 9, 2011 着払い
キャンセルされた 着払い

This database is for internal team with 2 project managers.

They need to manage multiple projects within the DB.

Switchboard should should have a dropdown box that holds the names of the project managers. When a managers name is selected the Landingpage form is displayed with content for the selected project manager only.

The landing page has the following tabs

The tab names are

Initiation

Implementation Planning

Development

Implementation

Publication

Evalute & Maintenance

Project Completion

When the user selects a tab she is shown a list of her assigned projects that are in that phase.

I also want the Project Manager to have the ability to add a project

When a project is added the following values need to be entered by the Proj Manager

Title - Could be the product title or a topic (for a place holder)

2. EPT - Primary EPT that will be publishing the product

3. Start Date - Assuming this would just be the date of the initial discussion?

4. New or Revision - Indicate which is the nature of the project. I don't think they would get into the detail for the reason of the revision unless it was a level 2 or 3 implementation, so I don't think we would want to hold up this phase...

5. Level of Implementation (Drop down level 1,2,3)

6. Documents to be Replaced

7. Champions or Contacts - This would be the section you mention as requestor? Or should there be a separate field to indicate who initiated the project?

I'm attaching what I've started

NOTE: Do not waste my time by posting your company info, links to your work without providing a bid for this project.

## Deliverables

Here is more details or info for each phase

Initiation

1. Start new project (order set, guideline, checklist, etc - referred to as products in my documents)

a. This will likely be in the form of a meeting, but could be via e-mail, etc

b. The initial pieces of information should be gathered which would include the following...

1. Title - Could be the product title or a topic (for a place holder)

2. EPT - Primary EPT that will be publishing the product

3. Start Date - Assuming this would just be the date of the initial discussion?

4. New or Revision - Indicate which is the nature of the project. I don't think they would get into the detail for the reason of the revision unless it was a level 2 or 3 implementation, so I don't think we would want to hold up this phase...

5. Level of Implementation

6. Documents to be Replaced

7. Champions or Contacts - This would be the section you mention as requestor? Or should there be a separate field to indicate who initiated the project?

Implementation Planning - Thinking that maybe those that are Level 2 or 3 enter another branch requiring fields to be entered.

Level 2 - Provide information for implementation planning

1. Key Stakeholders - beyond standard feedback groups

2. Tentative Agenda Date - Maybe Tentative Completion Date (will need to discuss the definition of this)

3. Elevator Speech

Level 3 - Same as above with the addition of...

1. Related process issues

1. Would perhaps set dates for implementation efforts from this as well, not exactly sure if anything needs to be logged though...

2. This may also be where beginning phase of OSU data are developed so there is a before imp and after imp measure comparison

Development

1. Upload or creation of draft

2. Approval of SMEs/authors for presentation to EPT

3. Solicitation of feedback

4. Revision by SMEs/authors

5. EPT Approval

Implementation

1. Where notices begin to go out on EPT meeting activities (minutes, summaries, etc)

2. Where various portions of the different Levels of Implementation are housed - several based on Level

3. This could also possibly be pre-pub imp and post-pub imp (however it would be best to measure)

Publication

1. Entry date of publication

2. May want to log some means of when the replacements are removed or planned to be removed

3. May just be able to use this to also log the date for next revision and to enter revision requests that occur throughout that time-frame

Evalute & Maintenance

Measurement reports are generated

Project Completion

1. Log when the transition is complete & other documents are replaced or may just be the publication date because some may never remove there...don't want to skew the data too badly...

ソフトウェアアーキテクチャ ウィンドウズデスクトップ

プロジェクトID: #3368776

プロジェクトについて

1個の提案 リモートプロジェクト アクティブ Jun 9, 2011

1人のフリーランサーが、このジョブに平均$51で入札しています

tendwasofts

See private message.

$51 USD 4日以内
(0件のレビュー)
0.0