General discussion


what is the right order for these tasks?

By nonname35 ·
Feasibility Study
Design New Network Bootstrap
Design network porting structure
Design configuration Program to set up CMOS RAM
Implement new network bootstrap
Initial test of MIS on existing hardware
Fault Rectification of program
Implementnew MIS modules
Investigate and Design New TCP/IP& network
Implement new TCP/IP& external MIS links
Test Plan for new network
Test network download code
Fix problem with network download code
Port MIS interface software
Port financial software
Port database software(for customer/suppliers
Design Training plan
Implement Training plan
Test stock interface software (3rd party)
Test plan for software(without modification)
Test for Telnet
Test for Web Browser
Test Email Software
TestWord processor
Test Spreadsheet
Test Diary manager
* After Deliver of Prototype
Initial load of software
Prototype Acceptance Test PLAN
Test of Network Related Software
Test of Ported Software
Test of non ported software
Support of initial prototype test and fault rectification
Support &maintenance during prototype alpha test

Thank you very much all your help in that matter

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

what is the right order for these tasks?

by ckilday In reply to what is the right order f ...

It looks like you're trying to design a new network for your company. Rather than rank each task individually, I suggest you consider some basic groupings and then sort the tasks accordingly. #1. For a proper design methodology, you need to research your current environment. Identify the physical bottlenecks (slow lines, old routers, hubs, etc...); capture information on the applications you are using and their demands upon the network; identify the resources you will have (money, personnel,etc...), and identify any organizational or political limitations. #2. Then you can move on to the design phase, where you identify new hardware, network protocols, data circuits and create the network topology. #3. You build the prototype network. Try to get an individual piece of each type of equipment you will be using and then borrow a number of workstations for an adequate user testing environment #4. You begin your testing phase (and it seems like you have plenty to test!). Don't neglect user testing! They can show you things you might miss, or screw things up in ways you can't imagine! #5. Plan your implementation. Do this in phases, unless your network is small enough that you can do the whole thing either overnight or overa weekend. Make sure you communicate your schedule to the users in advance. It will make the installation so much easier if the users know what's coming and when. Be prepared to handle questions and problems the morning after. BTW, your trainingplan for the users/technicians should be ready to go by now. #6. Install the new network. You will probably find it easier to install new hardware first, let it settle into the environment, and then incorporate new software and applications. You don't want to be troubleshooting too many variables if problems occur. Hope this helps you organize your tasks.
Best wishes
- ck

Related Discussions

Related Forums