I would like to thank everybody for working to their best this term, I had fun. I’m looking forward for more the next term

Just to recap some stuff:

• No meetings are needed for this term
• Wednesday, 27th Is our Senior Presentation at 2pm. You have to be there.
• For the presentation, Yazeed and I will take care of it
• The prototype will be given to everyone as soon as some documentation is there. Please explore it in the vacation. Documentation is already in the process.
• Explore and learn new stuff if possible during the vacation

Finally we are done with the White Box Testing.. If you want to check it out, here is the link:

Algoritms White Box Testing

Schema: Game

Tables in Schema

The Map data is decided to be individually implemented to be used by the parser that would work out the text file that contains the data of the map.

(For more information, go to Database Design)

Yazeed in game programming self-learning session

Abdullah and Emad in game layout decision while trying different games

Osama in Use Cases brainstorming session

Game trying to decide on the layout and storyline and graphics

Turki in the game trying session

We were also wondering if such use case modeling was possible: Nano Squad Use Cases 2

Finally, There are the state siagrams we could come up with. We are wondering if We can come up with more states in the project.

• In Game Aircraft status State Machine
• In game Action State Diagram
• Nano Squad State Transition Diagram

Finally, Our final document is here:

Nano Squad Use Case and State Transition Diagram

You can have a look at our vision document here: Nano Squad Vision Document

Nano Squad’s Software Project Management Plan’s goal is to list all the following:

1.      Overview.. 7

1.1.       Project Summary. 7

1.1.1.         Purpose, Scope, and Objectives. 7

1.1.2.         Assumptions and Constrains. 7

1.1.3.         Project Deliverables. 8

1.1.4.         Schedule and Budget Summary. 8

1.2.       Evolution of the plan. 8

2.      References. 9

3.      Definitions. 9

4.      Project Organization. 10

4.1.       External Interfaces. 10

4.2.       Internal Interfaces. 10

4.3.       Roles and Responsibilities. 11

5.      Managerial Process Plans. 12

5.1.       Start-up Plan. 12

5.1.1.         Estimation Plan. 12

5.1.2.         Staffing Plan. 12

5.1.3.         Resources Acquisition Plan. 13

5.1.4.         Project Staff Training Plan. 13

5.2.       Work Plan. 15

5.2.1.         Work Activities. 15

5.2.2.         Schedule Allocation. 19

5.2.3.         Resource Allocation. 21

5.2.4.         Budget Allocation. 24

5.3.       Control Plan. 25

5.3.1.         Requirements Control Plan. 25

5.3.2.         Schedule Control Plan. 26

5.3.3.         Budget Control Plan. 27

5.3.4.         Quality Control Plan. 27

5.3.5.         Reporting Plan. 28

5.3.6.         Metrics Collection Plan. 29

5.4.       Risk Management Plan. 29

5.4.1 Risk categorization table. 30

5.4.2 Top 10 risks. 30

5.4.3 Risk response. 30

5.4.4 Risk change. 31

5.4.5New risks. 31

6.      Technical Process Plans. 32

6.1.       Process Model 32

6.2.       Methods, Tools, and Techniques. 32

6.2.1. Methods: 33

6.2.2. Techniques: 33

6.2.3. Tools: 33

6.2.4. Team member desktop foundation. 33

6.2.5. Project management. 33

6.2.6. Document publishing (applies to all documents published by the project). 33

6.2.7. Configuration Management and Change Management. 34

6.2.8. Requirements. 34

6.2.9. Software Design. 34

6.2.10. Implementation. 34

6.2.11 .Testing. 34

6.2.12. Training. 34

6.3.       Infrastructure Plan. 34

6.3.1. Working Facilities: 34

6.3.2. Desktop Setting: 35

6.3.3. Network configuration: 35

6.3.4. Software licensing: 35

6.4.       Product Acceptance Plan. 35

6.4.1. Project documentation. 36

6.4.2. Project milestones. 36

6.4.3. Penetration Software. 36

6.4.4. Installation of Penetration game. 36

7.      Supporting Process Plans. 37

7.1.       Configuration Management Plan. 37

7.1.1.         Configuration Management Tools. 37

7.1.2.         Configuration Identification Method. 37

7.1.3.         Configuration Control Mechanisms. 37

7.1.4.         Status Accounting Method. 38

7.1.5.         Evaluation method. 38

7.1.6.         Procedure for change logging. 38

7.1.7.         Procedure for change request meetings. 39

7.2.       Verification and Validation Plan. 40

7.2.1. V&V Responsibilities. 40

7.2.2.         V&V Tools and Techniques. 40

7.2.3.         V&V Reviews. 41

7.2.4.         V&V Plans. 41

7.2.5.         V&V Reporting. 41

7.3.       Documentation Plan. 41

7.4.       Quality Assurance Plan. 42

7.5.       Reviews and Audits. 43

7.6.       Problem Resolution Plan. 44

7.7.       Subcontractor Improvement Plan. 45

7.8.         Process Improvement Plan   49

All these are very important when dealing with any kind of project, and it is good practice to do this for different kind of projects. The things listed above may differ from other templates because some fields were not applicable.

You can download and view our document from here:

Nano Squad Software Project Management Plan

If you do have any comment regarding our project plan, please do tell us =) we welcome any kind of feed back.

We try to follow software engineering techniques making our game. We strive to do our best in order to achieve this specially when our collage does not have any game courses and don’t teach us special stuff about games in general.

There should be a weekly post to this web blog, see keep tuned

Feel free to send us mail and help us in anyway possible.

Before I leave, I would like to tell you roughly what is Nano Squad.

Nano Squad is a multiplayer game aimed to be released for Xbox 360 a year from now. Its core is a collaborative game play were 4 players play as 4 different aircraft, each have different specialty which others don’t have. They can merge in order to support each others’ weaknesses.

The game will be 2D side-scrolling based.

Thanks.

~Abdullah Konash

Project Manager.