ICT-581 Assignment2 - practice writing a plan to define a project’s requirements Solved 

        In this assignment, you will practice writing a plan to define a project’s requirements (consult Assignment 3 for more info about the project). You will need materials from lesson 3 to complete this assignment. Please check the instructions and requirements.

 

In assignment 3, you will create your first ‘mobile-fit’ web application. The project is about creating a simple to-do list. For now, in Assignment 2, you will need to write a plan, and you will start by identifying project requirements, designing an application interface, and sketching a prototype. 

◼ Instructions
1.    Your plan should be organized in three sections: 

a.    The first section (Description section) contains your description and conveys your understanding of the project. This section should answer the questions: “What do you want to make?” and “What technology will you use?” Please consult slides from Lesson 4 for guidance.

i.      “What do you want to make?”

1.    Specify the steps required to accomplish the project objectives.

2.    List the tasks that must be completed at each step (using Work Breakdown Structures).

3.    Estimate how much effort each task will require.

4.    Itemize the resources required for each task.

ii.     “What technology will you use?”

1.    Determine which languages you will use (e.g. HTML, CSS, JavaScript).

2.    Identify the most effective libraries (e.g. jQuery, Bootstrap).

3.    Select your environments (e.g. cross browsers).

b.    The second section (Features section) contains all the information about the project (application) features. You must draw a chart for each feature and identify the process flow between features. You need to address only those features listed in Assignment 3, beneath the heading ‘instructions’. This second section should answer the question:

“What features will the application include?”

c.    The third section (Prototype section) contains all the information about the project prototype. You must provide a design and height level chart. The prototype should show the feature and process flow, and specify how these processes relate to each other.    

2.    Things to keep in mind: 

a.    The project features (code) should be divided into units of (tasks/steps) functionality: modules, services, and so on. Avoid the temptation to have all your code in one huge $(document).ready() block. This concept, loosely, is known as encapsulation.

Page  of 3
           

b.    Despite jQuery's DOM-centric nature, JavaScript applications are not all about the DOM. Remember that not all pieces of functionality need to—or should—have a DOM representation.

c.    Units of functionality should be loosely coupled: That is, a unit of functionality should be able to exist on its own, and communication between units should be handled via a messaging system such as custom events or pub/sub. Stay away from direct communication between units of functionality whenever possible.

◼ Requirements 
1.    The project plan must include all three sections: the project description, features chart, and project prototype. 

2.    The document should be formatted as follows:

a.    The font size must be 12 points. 

b.    The font type must be Arial.

c.    Headlines should appear in bold, and paragraphs in a regular, unbolded font. 

3.    The project plan should not exceed three pages. 

4.    Do not repeat yourself. Identify similarities among pieces of functionality and use inheritance techniques to avoid repetitive features.