Page 56 - SPM FINAL

DATE 06/01/2020

SUBMITTED BY RA1811003020013 Ritesh Singh
RA1811003020034 Shubham Nandi
RA1811003020032 Yash Bha

TITLE / ROLE Nework Helper Using Kruskal's & Dijskstra's Algo

Specific So ware Development Process for Network Helper (NWH)

Conclusion

It has become clear that the so ware development processes for netwok helper can be par ally different from
conven onal so ware development processes regarding
● the types of tasks
● the order in which the tasks are performed
● the roles that perform the tasks
● the so ware tools used
For this reason, it makes sense to examine conven onal so ware development processes with regard to their op mal
suitability ( me, cost, resources) for this new class of so ware systems.
The development process for the NWH is characterized by the high effort that was necessary to integrate the
subsystems. This experience can be transferred to the development of other NWH systems, because the system usually
always has to be integrated into a pre-exis ng so ware and hardware infrastructure. The integra on effort comprises
not only the design and realiza on of interfaces (APIs), but also the test of those interfaces. The more complex the
subsystems are, the more effort is required for the interface test since the necessary test drivers and stubs have to be
equally complex.
Every introduc on of an NWH system on the market should happen " me-to-market". Consequently, an es mate of
the feasibility, effort and especially the dura on of the development project has to be made early. A solid es mate of
these factors can be achieved through incremental and itera ve prototyping.
As in every so ware system, features suppor ng the user (e.g. a self-explanatory user interface and online help) should
not be neglected in NWH systems, either. It is important that the user-suppor ng features are tailored to the intended
audience of the NWH system.
The same is true for NWH systems used in an intranet, like the electronic commerce portal for insurance agents. The
so ware development process must contain tasks for the crea on of these features.
The way the user interface of an NWH system is designed significantly contributes to the user acceptance of the
system. This means that the so ware development process must include the crea on of a user interface prototype that
can serve as a marke ng tool and be a basis for discussions with ergonomics specialists. For host-based applica on
systems, the user interface design opportuni es are limited. Here, acceptance must be based on func onality.
Unfortunately, quality-assuring measures can be vic ms of the " me-to-market" philosophy. This is true for all NWH
system development projects and can also be observed in the development process for the IPSI electronic commerce
portal. However, the goal must be to model so ware development processes that ensure a consistent high quality of
NWH systems despite the changed and dynamic condi ons, and take into account the shorter development mes for
these system