74109683_ R1901D7421833 Page 1 of 41

University of South Wales

MBA-Masters in Business Administration

September, 2021

Management Project (BS4D03-V1)

USW NUMBER: 74109683
UNICAF NUMBER: R1901D7421833
STUDENT NAME: AZUBUIKE JONATHAN NNAMDI

Tutor: Evangelia Katsikea

 74109683_ R1901D7421833 Page 2 of 41

Management Summary

On a daily basis, every organization are looking for innovative ways to be quite

competitive and more efficient in ways of achieving their aims and objectives, in this 21st

century this can almost be impossible without the incorporation of technology in their

business models. This extends to different business interactions which includes the

business to customer (B2C) transaction where there are sales of products directly to

customers, and the business to business (B2B) interaction where there are transactions

between businesses like manufacturers to distributors, wholesalers to retailers or

distributors to wholesalers.

One of the innovative and efficient ways of incorporating technology is by development of

mobile business app. This to a large extends saves time, improves and monitors

productivity, and it is being widely accepted and used by most organizations like transport

companies, distribution of drugs in pharmacy, grocery stores, distribution of clothes etc.

There are various software and applications designed to support the goal of an organization

and thereby serve as a background for making strategic decisions and solution based

software incorporated apps. A company Y which business is distribution of drugs from

them as manufacturers to her distributors, has realized the importance of B2B mobile

applications in their operations and intends to use it for fast and accurate efficiency in

operations.

This paper aids to determine required information needed for development of mobile B2B

app and its implementation. This will focus on past experiences based on case studies,

techniques and methods. It also discusses the three relevant categories of requirements. For

the Functional Requirements, the stakeholder analysis and software benchmarking are
 74109683_ R1901D7421833 Page 3 of 41

discussed for company Y. Personnel analysis, system environment analysis, risk

identification and analysis are the rudiments for future decisions. All these are discussed

under the Structural Requirements.

Lastly for Resources Requirement, project time planning and life-cycle cost analysis for

company Y shall be discussed. The study will utilize the Gantt-chart to illustrate the

schedule, sequence and progress of the task within the 6 months (26 weeks) timeframe and

its progress throughout the project. Extractions will be made from these categories, the

benefits, contribution and recommendations are thereby made available to the client, based

on their defined objectives to make the study of superior value, and provide adequate

information for further actions regarding the application’s programming and

implementation process.
 74109683_ R1901D7421833 Page 4 of 41

TABLE OF CONTENTS INDEX

CHAPTER ONE
1.0 Introduction - - - - 5
1.1 Study Objectives - - - - 6
1.2 Methodology - - - - 8

CHAPTER TWO
2.0 Supporting Evidences - - - - 9
2.1 Objective 1: Functional Requirements - - - - 9
2.1.1 Stakeholder Analysis - - - - 10
2.1.2 Software Benchmark Testing - - - - 11
2.2 Structural Requirements - - - - 13
2.2.1 System Environmental Analysis (ESA) - - - - 14
2.2.2 Personnel Analysis - - - - 15
2.2.3 Risk Identification and Analysis - - - - 17
2.3 Resource Requirements - - - - 18
2.3.1 Project Time Planning - - - - 19
2.3.2 Life Cycle Cost Analysis - - - - 20

CHAPTER THREE
3.0 Study Gantt Chart - - - - 22

CHAPTER FOUR
4.0 Contributions - - - - 25
4.1 Functional Requirements - - - - 26
4.1.1 Stakeholder Analysis - - - - 26
4.1.2 Software Benchmarking - - - - 27
4.2 Structural Requirements - - - - 28
4.2.1 System Environmental Analysis - - - - 28
4.2.2 Personal Analysis - - - - 29
4.2.3 Risk Identification and Analysis - - - - 31
4.3 Resource Requirements - - - - 32
4.3.1 Project Time Planning - - - - 32
4.3.2 Life-Cycle Cost Analysis - - - - 33

CHAPTER FIVE
5.0 Conclusion - - - - 34
References - - - - 36
 74109683_ R1901D7421833 Page 5 of 41

1.0 Introduction

The introduction of technology has enhanced our knowledge, methods, and giving us new

ideas on how to carry out our daily business activities which has aided in making the lives

of mankind easier. In this circumstance, it is majorly organized by mobile apps. These

direct electronic alliance are fondly categorized as business-to-business applications (B2B).

These applications are stored in devices which has the capacity to connect with internet

through smart phones, laptops, iPads, PC etc. There are increased usage of internet services

worldwide which especially involves the use of mobile B2B applications which has

therefore been regarded as a principal tool for managing a good customer relationship

(Smilansky, 2015). This internet access helps in facilitating connectivity and partnership

electronically between business people and their clients, business conditions, behavior of

consumers and opportunities in the market have been changed extensively by technology

(OECD 2004; Dahlstrom et al., 2015; Daniel, 2016). In recent times, the public prefers the

use of mobile applications than the use of the old fashioned desktop computers because it is

much easier and faster (Zamfiroiu, 2015).

According to discovery, quite a number of businesses are making good use of the

opportunities in obtaining mobile software to achieve the purpose of B2B connections for

customer’s contentment (Chris et al, 2003). Upon the development, well known

manufacturers results in offering mobile B2B applications for multiple business purposes

(Tornack et al, 2011). Having Company Y as a business, customers can to a great extent

make much profit from the use of M-commerce because they possess restricted assets in

terms of good management of funds and manpower (Zhao, et al, 2016). This restricted

assets clearly suggests that very limited funds are accessible to disburse for retail and
 74109683_ R1901D7421833 Page 6 of 41

publicity, therefore M-commerce can assist company Y in reaching out to a lot of people

around the world (Bagozi, R.P., 2009).

The purchaser, company Y having full knowledge about the mobile B2B applications

decides to implement the usage in achieving maximum customer satisfaction in her

distribution of drug products to various pharmaceutical companies. To decide the essentials

in order to grow a B2B mobile application in light of this positive evolution, Company Y

will have to devise a means of involving a consultant to conduct an overview study.

In various project researches, over hundred results have proven that majority of project

successes, are strongly tied in the visibility of those requirements (Dvir et al, 2003). In

order to dictate relevant requirements of this project, a study should be carried out to

provide vital information about different project essentials. Therefore, previous

identification and careful analysis of various non-functional requirement are needed as

summarized by Veronica et al., (2014), before Software is developed and incorporated into

the business. Concerning software development, this process is often called ‘requirements

engineering’ respectively ‘requirements elicitation’ which describes “seeking, uncovering,

acquiring and elaborating requirements for computer based systems” (Zowghi and Coulin,

2005, p. 19).

1.2 Study Objectives

In overall, the purpose of this research study is to make sure that the enterprise, Company

Y is well pleased to investigate the requirement and still aimed in achieving the goal of the

project. As a result, incidences derived from research studies on software management and

methods involved in project management will take a vital role in the stated requirement for
 74109683_ R1901D7421833 Page 7 of 41

an impression approach. The study describes the objectives and methods in order to

disclose information and requirements needed for the development and implementation of a

standard mobile B2B application, where we have the goals and procedures being

combined:

Objective 1: Identification of the need to have a functional B2B software, which aids in

creating a good customer contentment.

 Software benchmarking.

 Stakeholder’s analysis.

Objective 2: Identification of the systemic conditions needed for the implementation and

plan of the software applications which contributes to the potentials of the existing

company.

 Risk Identification and analysis

 Systematic Environmental Analysis

 Personnel Analysis

Objective 3: Funds are needed to have a standardized and operating mobile B2B program

application. Therefore the financial strength of the client is a vital item to be observed

 Life-Cycle cost analysis

 Project time planning

 74109683_ R1901D7421833 Page 8 of 41

1.2 Methodology

In this offer, there will be a demonstration of procedures which are needed to disclose

essential conditions in the three objectives. An extensive output of the software, B2B

application is solely dependent on the qualitative configuration approach used in the setup.

Therefore, the amount of quality input will either contribute to a successful software output

or to its abortion. As a result of the estimated time needed, this offer will introduce the use

of Gantt Chart which will help in the survey of the various methods and step of each

project, starting from the beginning to its end.

There will be an assessment survey to be carried out because there’s a speculation that it

contains the crucial knowledge needed for the programming of the software. Afterwards,

the company will be impressed that its objectives has been clarified due to the input of this

specific method. Lastly, the closing remark tells us about the main purpose for this offer,

and this is to give ideas and steps on how to carry out the final decision made on the offer.
 74109683_ R1901D7421833 Page 9 of 41

2.0 Supporting Evidence

This chapter in details explains the individual steps and procedures involved in organizing

the usage of the mobile B2B application. It includes all relevant information and

accessibility which are geared towards providing a comfortable approach for the client.

Clients are being invited for an open dialogue, so as to be informed about the steps and

processes involved. In most cases, clients can request for some changes in their

requirement during clarification and this should be added immediately the change is

recognized. According to Nakatani et al., (2014), to tighten the acceptability of this study, a

continuous interaction with the client should be created, and this is to improve familiarity

and comfortability. Houdek and Pohl (2000) who encouraged the above action took some

time to examine the processes involved in the clarification of Daimler-Chrysler research,

and he stressed that more than 50% of the requirement swap occurs after the recognition of

the procedures. This chapter will discuss about the circumstances involved in this particular

procedure, and also the single steps taken towards achieving its goal.

2.1 Functional Requirement

As already mentioned above, B2B software applications explains so much about its

usefulness and efficiency as a supplier exchange (electronic procurement) , involving sales

and easy payment, not only as an advertising device (Al-Naeem et al., 2005). An

application is said to be excellent, if its efficiency adds a huge advantage to its prospective

users, thereby providing satisfaction to the customer. When there are no user-target in the
 74109683_ R1901D7421833 Page 10 of 41

programming of B2B, it simply results to non-success of the application (Sandler, 2005).

There will be an evaluation about the principle features which adds advantage to the mobile

software application which also improves B2B correspondence. In general, the client will

be educated concerning what the labor market expects of the B2B software application.

The development and programing of software application for the use of daily businesses

has indeed assisted greatly to decrease the difficulties and challenges encountered by the

client, thus contributing more value to the business. When a business-to-business

interaction is not familiar with the end user, lacks appropriateness, with no focus, then it all

leads to an unsuccessful business -to- business (B2B) connection, and the final outcome

results during the struggle becomes unproductive (Sandler, 2005). In the course of this

study, we will be observing and taking notes of some essential features that will improve

the implementation and programming of the mobile software app. This also gives guidance

and steps taken in the gradual process of the software application and its role.

2.1.1: Stakeholders analysis

Just as Glinz and Wieringa, (2007); and Newcombe, (2003) has summarized, stakeholders

analysis is a major tool in the execution of project management and is publicly recognized

among researchers and professionals in management as a condition for an evocation

procedures. The entire process helps to provide important information which are needed in

the course of the project. The analysis of stakeholders involved in the software

development are persons, groups or organizations whose actions affect or are affected by
 74109683_ R1901D7421833 Page 11 of 41

the software (Power, 2010). This procedure tends to ascertain the overall relevant

stakeholders, ranked or compared in their quantum of relevance, needs and wants explicitly

identified. The different stakeholders have varying expectations for the software, making

their wants and needs different, which could cause conflicts between them (Newcombe,

2003)

As proposed by Calvert (1995), a brainstorming meeting is required for the identification

process of stakeholder for the client. The meeting is organized to deliberate on the

recognition process of the stakeholders. The client participates because of his/her higher-

level of knowledge in regards to the affected groups and domestic procedures (Pouloudi

and Whitley, 1997). The identification process focus on the ‘Baseline Stakeholders’ as

proposed by Sharp et al. (1999, p.389), which refer to the external and internal developers,

decision makers and legislators in direct relation to the complete expected software cycle

(Dissertation Project, 2016). After the pertinent stakeholders have been dutifully identified,

demands/necessities are being communicated through a direct connection with the

stakeholder. Avenues such as meetings and one-on-one dialogue sections serves as a means

of passing information across (Passenheim, 2009). This procedure encourages the

stakeholders to participate from the start to finish of the proposed project. Struggles

encountered in the availability of stakeholders can result to facing many challenges while

performing the stakeholder’s analysis in a diversified organization, such as the presence of

some individuals with different intentions (Jepsen and Eskerod, 2009).

2.1.2 Software Benchmarking:

There are so many software applications programmed in several mobile devices found in

the industry which has been specifically designed for businesses that contains so many
 74109683_ R1901D7421833 Page 12 of 41

operating system (OS) while the client gets maximum satisfaction due to its user-friendly

feature (Pizzutillo, 2015). To enable the client enjoy the full benefit of the software, there

should be a careful computing of benchmarks together with accessible data base.

Benchmarking involves a competitive assessment of the software program, into finding out

its unique characteristics which are greatly used in business and other sections. In software

benchmarking the main target is centered on the workability of the software which the

stakeholders has pointed out as the highlight. Benchmarking best narrates the process of

comparing self-organizational IT programs with other software programs from other

organizations. Consequently, applying this information and acquired knowledge will

greatly improve self-business performance (Watson, 1993). Therefore, a good definition of

software benchmarking can be recognized as a targeted competitive analysis that is

incorporated alongside with software companies as the best course of action for equivalent

market. The possibility of establishing a functional requirement of a client can be derived

using the pattern of an outward benchmarking analysis, this helps the client to stand firm

and participate on a technical, top-level and on a subjective grounds with his competitors

(Hines, 1998).

According to (Kodali, 2008), the introductory procedure of software benchmarking is for

the assembling of information (data), whereas the major concern of benchmarking which

are contenders and software industries are ready to kick start work. Data bases from Market

lines, Key Notes and Mintel are good sources of information during an extensive report

after sales, and also being the suppliers of an exceptional benchmarking reports such as

LLC and Best-Practice. More so, manufacturers such as Microsoft, SAP and Oracle whose

invention have ascertained a high level of visibility in terms of software programming, and
 74109683_ R1901D7421833 Page 13 of 41

offers additional information for mobile solution which are needed in various sub industries

as well as in the pharmaceutical industry. Subsequent analysis and assessment are being

carried out on the collected information (data). Information gotten from the analysis are

being differentiated, and the motives of the stakeholders are being extracted together with

the detailed benchmarks. This is done in order to draw a concluding functional

requirements where the mobile B2B software application has to satisfy the client’s

objective, so as to realize a feasible competitor superiority within the industry (Kodali,

2008).

2.2 Structural Requirements

The essential functions of the B2B software application were uncovered as a result of

previous technique, and the questions extracted are basically derived from the following

procedures, among other contemporary administrative environment, the client will have to

satisfy the structural requirement needed in planning and executing the development of an

application with such features. The employees and also the risk dimensions takes part in a

crucial role and their control over certain issues, even when the client is not able to proffer

solutions according to control digression and dangers about to occur or if there will be an

alternative assistance from an external workforce service provider.

2.2.1 System Environment Analysis:

The structural requirement analysis is the platform which the system environment analysis

has provided. This is an arranged procedure for narrating human activities which has
 74109683_ R1901D7421833 Page 14 of 41

affected the natural surroundings so as to support settlements and behaviors targeted at an

assumed current situation or a foretold negative circumstance waiting to occur (Kogdenko,

V.G., 2011). Afterwards, the system environmental analysis has to scrutinize whether it

will be demanding to organize and implement certain features and functions in the client’s

information technology system environment. For the requirement elicitation steps to be

carried out systematically, this procedures are very essential because of how important it is

to implant into the B2B software application onto an existing system environment

(MacLean et al., 2004).

The invention of software benchmarking has greatly assisted to make sure that a practical

prerequisites has well pleased the stakeholders and their various objectives being carefully

evaluated in the grid of stakeholders, the environmental study of the system will assist us to

survey the existing environment in which the requirements are developed and executed in

the information technology system environment of the company (Madden, T.J et al., 2006).

According to Pries and Quigley, (2008), the analysis should comprise of the interfaces and

extensions (after) which are found among the new B2B mobile software application and the

existing system environment, extensions and interfaces (before) and the required system,

lastly, the recognition of the existing systems to be contained in the analysis. More so, the

existing information technology (IT) service has to be revealed. During the programming

of B2B software application, support and safety procedures has to be considered.

Surveying more requirement that may be gotten from the symbol will disclose that there

are possible condition for extension adoption. On the grounds that some systems are

pretentious, it is usually common and feasible to pick out a certain type of information

technology (IT) services expertise, which could be needed so as to control these effects.
 74109683_ R1901D7421833 Page 15 of 41

The invention of mobile devices has helped to effectively involve the clients. Constraints

are created that require examination as to whether they can be managed by clients as a

result of integration of changes into interactive systems and their system environment

which constitutes part of the operational enterprise according to Liu et al. (2016) that has

the involvement of other entities (Bedell, 2013).

New software are intentionally created for the businesses, for customers to come across

new software, and to be able to install it successfully, this gives the user a good satisfaction

and wonderful experience and will always remain faithful (EMarketer, 2006).

2.2.2 Personnel Analysis

The following features that has been found very necessary and essential to be incorporated,

organized, and applied into the system’s environment, are realized to have worked very

effectively alongside with the system’s environment, this makes it easy to look into the

personnel assets, which are essential to organize it. In this analysis, it is important to know

what resources the client can provide based on the required employees and the designated

skills needed for the project.

A consideration should be given by the counselor on the method of the project's

incorporation into the company and the formation of the teams; MindFit Consulting (2018),

concluded that the client will have to require the personnel assets to be aware of how to

manage the expertise for this project which includes the performance and development of

the mobile B2B software application. According to Project Management Institute, (2013),

the commencement of a project work can only be successfully completed or executed, If

the client is convinced enough to provide the number of the essential workforce and their
 74109683_ R1901D7421833 Page 16 of 41

various handworks/skills, that are basically required for the performance and development

of the mobile B2B software application. Therefore a personnel analysis has to show how

much the project industry is incorporated together with the organization, and equally how

organized the members of the team should be (Passenheim, 2009).

Functional requirements are selected roles which are derived from role planning that were

selected to note the environmental analysis results and also point out the 1st procedures

involved in the project. While deliberating on the practical task and the managerial duties,

there should be a set aside project task within company Y’s grading order, (Jucan, 2013).

Administrators and the other workforce of the company are extensively coached/ tutored to

gain and have knowledge of important skills, and this coaching process can be entirely

complex, therefore, a systematic personnel analysis that differentiates duties and

obligations of the human assets of the client should show exactly what the personnel

requirement needs for the task ahead (Otero et al., 2009).

Henceforth, the personnel analysis shows the real state analysis by differentiating ‘what is

needed’ alongside with ‘what is present’. The tasking duty in this analysis is by

representing the opening move. For safe keeping, recording the information of the

functional assets alongside with the organizational environment analysis as a ground.

Important duties should be identified and delegated the specific personnel that match the

skill required for such task.

 74109683_ R1901D7421833 Page 17 of 41

2.2.3 Risk Identification analysis

Risk identification analysis is the final process we have in structural requirement.

According to Nicholas and Steyn, (2012), risk identification, analysis, planning and control

are usually embedded in the project risk management. The purpose of evaluating the

structural requirements involved in the execution of a client’s request is to take note that

the project needs the implementation of the initial first and second steps. According to a

comprehensive statistics, which was diligently carried out, it was recorded that risk

management approach tops the list of the important process in the composition of every

project (Passenheim, 2009).

In spite of the fact that total removal of hazards is generally impossible, to identify and

control is the regular remedy (Nicholas and Steyn, 2012). So many components can result

to project risks within every project step (Lock, 2013). In addition, it has been proven that

it is either established on inner or outer factors (Maley, 2012).

In order to prevent future damages and hazards, there should be a proper investigation of

risk level that could happened, and this should be categorized in the order of their risk

level; this should be carried out as soon as the possible risks to the project has been

identified. A show of the risk potentials and level of hazards that can be possibly created

will be identified using the ordinal scale matrix (high, medium and low) as well as the

quantitative risk impact on cost estimation result (Passenheim, 2009; Maley, 2012). The

next is to rank the risk in a matrix based on the assessment made.

The risk identification and analysis should be carried out as an overarching process (see

Gantt chart) because risk identification and analysis affect numerous requirements
 74109683_ R1901D7421833 Page 18 of 41

elicitation areas such personnel, IT, time and costs risks. This strategy ensures that there are

no gaps in the identification process, considering the likelihood that other methods also

reveal additional risks.

2.3 Resources Requirements

After it was disclosed that for there to be a successful programming of mobile B2B

software application, structural requirements must be executed. Traditional project

management arrangement should possibly be organized so as to know the essential assets

the client has to bring up. The essential resources must in all probability make-up of the

most reasonable type of requirements, and this is because they are capable of expressed

quantifying numbers. Generally, this research analysis unravels the length of time involved

in the execution and engineering of the programmed software procedure (and that includes

the essential trial and collaboration process) will consume and the financial assets that are

greatly needed to coordinate the project and be responsible for the expenditures involved

alongside.

2.3.1 Project Time Planning

Sequentially like every project, separate procedures will have to be carried out in the

programming of the customer’s mobile B2B software application. To be successful in the

surveying of time the organization will have to spare for the success of the project, and to
 74109683_ R1901D7421833 Page 19 of 41

be able to disclose the provisional requirements for the essential procedures, organizing

project time is needed. This mostly involves the projects from the software engineers. Time

taken clearly represents a particular provocation because of the extreme complexity and

dependence on probable procedures no one is sure to happen (Lock, 2013).

The first step is to get the foundation for the scheduling activities and estimation breaking it

down from one activity to the other and their dependence on the actual to the former

activities. This step needs testing procedures and excellent knowledge in software

programming, therefore managers that have prior experience in software engineering

projects and case studies are quite useful for the support of this step. Those sources,

combined with published estimation data, are required to contribute to the identification of

the approximate required time (Project Management Institute, 2013). Next, the step by step

activities that has been revealed will be put into a logical sequence. Individual task

durations and dependencies allow for drawing a network diagram, based on the start times,

end times and milestones (Passenheim, 2009). Although for the scope of this study which is

not relevant where more detailed method in planning would also look at resources

constraint and costs for each step (Nicholas and Steyn, 2012).

In the process to know the total time taken to perform each duty, suggestions such as Al-

Naeem et al., (2005, p41-70) discussed the total number of movement which are involved

in sketching a portrait that can assist the network and afterwards, explain each details.

Moreover, a Gantt chart which carries a lot of information will be talked about in chapter 3.

In addition, a well detailed and extensive plan where their financial challenges and

formulated assets are costlier to industry.

 74109683_ R1901D7421833 Page 20 of 41

In general, Microsoft project which is part of the project management software is primarily

used for projects that are known to be difficult and aids to prevent errors which may occur

and protects the safety of the planning procedures. Additionally, it creates so many options

for the customer in respect to the records and arrangement of the time planning (Zhang and

Bishop, 2013).

2.3.2 Life-Cycle Cost Analysis

According to Van, A.J, (2001) the method involved in discovering the total value of the

potential ownership is through the use of a Life Cycle Analysis (LCCA). Therefore, Life

cycle cost analysis is specifically important in the demonstration of the project which has

options that shows equal operation. In summary, project life cycle cost analysis is a

procedure appreciated in the assessment of the economic value of a project (Vargo, S. L et

al., 2004).

Consequently, Lindholm and Suomala, (2005) explains that Life cycle cost analysis can

also be illustrated in the proposed planning phase, on the condition that there will be an

early survey over a long period range. Various software products have varying life cycle

phases with linked costs. However, without an appropriate analysis, many of this costs are

hidden and therefore not factored in LCC (Eckardt et al., 2014). To determine the monetary

requirements of the mobile B2B application, Life cycle cost analysis pose to be an

important approach for the client because apart from containing implementation costs and

the relevant programming, it also contains follow up costs like maintenance, operating,

disposal and supporting costs starting from the beginning of the product to the end
 74109683_ R1901D7421833 Page 21 of 41

(Nicholas and Steyn, 2012). This approach is quite necessary since those costs are

interrelated to one another: Maintenance cost in the operating phase could be increased due

to a strategy to reduce cost in the development and testing phase of the product

(Passenheim, 2009).

The life cycle analysis are made up of five separate types of funds which includes the

following; external funds, contingent, direct, indirect, and intangible costs (Norris, 2001).

For example, these can be in form of labor, overhead and material cost (Passenheim, 2009).

The subsequent collection of information procedures which are applied for life cycle cost

analysis occurs with the aid of a bottom-up approach, applying costing based on

accumulated activities (Vlachy, 2014). In order to identify the functional steps required, the

software life cycle will be separated into different stages (Kapp and Girmscheid, 2005).

Nevertheless, the risks involved in life cycle cost analysis depends on its undependability

of information. With time, costs can change, and the analysis might not anticipate this

future changes in cost (Higham et al., 2015). It is therefore important to note that this

should be rather seen as an orientation and not a solid fact. In the instance of a total project

implementation, the estimated costs will eventually be on the grounds of performance

knowledge and details, thus increasing its reliability (Passenheim, 2009).

3.0 Study Gantt-Chart

All the steps implemented have various process durations and are all linked in their varying

techniques. The Gantt chart is a widely identified useful tool for providing an overview of

the steps and processes for consulting project for a client, stakeholders and consultant
 74109683_ R1901D7421833 Page 22 of 41

(Locke, 2013; Nicholas and Steyn, 2012). It is basically a bar chart that breaks down the

schedule of project, it was named after Henry Gantt who designed it (Zobel, T. et al.,

2002). The chart considers the individual implementation duration of each project step and

their dependencies. On the vertical axis it shows the required activity while the horizontal

axis reflects the time interval involved. The duration of each task is shown by the width of

the horizontal bar. The dependence on the Gantt chart is shown from the start to the finish

dependencies, this means that it shows which activity has to finish before the other begins

i.e precedence network relationship between activities (Bhattacharya, C. B. et al., 2008). In

another way, the major path that decides the project duration, critical path are exemplified,

this is the critical steps that have to be completed for the whole project to finish (Maley,

2012). The Gantt chart enables workability in the event of any unforeseen circumstance by

providing contingency plans for problems that were never expected and thereby executed

on the overall.

The study is slated to last for a period of 26 weeks (6 months). The chart begins with an

inaugural meeting for the project to kick off where all stakeholder will be introduced and

necessary information and resources shall be presented for the individual techniques and

particular steps (Passenheim, 2009). There will be a continuous communication between

the client and consultant to ensure proper adequacy of the study. This is very key bearing in

mind the ultimate goals and objective of the client to ensure satisfaction at her end.

Although the first 22 weeks are part of the processes in data gathering, the project

information will be shaped in week 23 to 25 and thereby produce the study.

 74109683_ R1901D7421833 Page 23 of 41

So long as the risk identification and analysis overlaps on each other and this includes

numerous factors, future adoptions can be made during the analysis of the resource

requirements. The client will receive the final report as well as recommendation for further

actions in the final week. Also, an evaluation meeting can be set up for both sides to

provide feedbacks for improvement of following consulting projects.

The Gantt chart is illustrated in figure 1, the sequence of the particular methods, their

dependencies and durations. The task ID helps to orientate and to distribute the

dependencies. In the chart, the filled cells are represent the conducted task, while the

dashed cells reflects that at that point, the individual tasks are ancillary. Grey cells shows

slack time, which shows that the individual task will take a longer time, but this does not

increase the maximum duration of the project since the critical path is not affected.

However, since the activities on the study overlaps on each other, the Gant chart does not

give much space for slack time. It will be safe to say that the project times were estimated

permissively, therefore no major delays are expected.

 74109683_ R1901D7421833 Page 24 of 41

Timeframe (6 months = 26 weeks)

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
w eek 2 6
1
2
3
4
5
6
7
8
9
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
w eek
Gantt

Critical Path 2 11 23 32 36
Task ID Task Duration Dependencies
1 Inaugural Meeting and Continous Communication 1 week ---
2 Objective 1 = Functional Requirement 7 weeks 1
3 Stakeholder Mapping 4weeks 1
4 Stakeholder identifi cation 1 week 1
5 Stakeholder meeting/conversation 1 week 1, 4
6 Stakeholder Prioritization 2 week 1, 4
7 Stakeholder Matrix (Incl. Prioritization and Objectives 1 week 1, 4, 5, 6
8 Software Benchmarking 3 weeks 3
9 Data Collection Process 1 week 3
10 Benchmark Analysis 2 weeks 3, 10
11 Objective 2 = Structural Requirement 8 weeks 2
12 System Environment Analysis 3 weeks 2
13 Interview with the IT Leader/Application Owners 1 week 2
14 Producing of IT Enviroonment Graphics 2 weeks 2, 13
15 Need Analysis 1 week 2, 13, 14
16 Personnel Analysis 3 weeks 12
17 Project Role Planning (which roles are necessary?) 2 weeks 12
18 Actual State Analysis (Does the company have the staff ?) 1 week 12, 17
19 Risk Identification and Analysis 8 weeks 2
20 Risk Identifi cation 4 weeks 2
21 Risk Evaluation 3 weeks 2, 20
22 Risk Ranking (Matrix) 2 weeks 2, 20, 21
23 Objective 3 = Resources Requirements 7 weeks 11
24 Project Time Planning 3 weeks 11
25 Project Beak Down and Time Estimation 2 weeks 11
26 Draw Network Diagram 1 week 11, 25
27 Draw Gantt Chart 1 week 11, 25, 26
28 Life Cycle Cost Analysis 4 weeks 24
29 Analysing Types of Cost and Necessary Activities 2 weeks 24
30 Data (Cost) Collection for Revealed Activities 2 weeks 24, 29
31 Cost Accumulation 1 week 24, 29, 30
32 Producing The Study 3 weeks 2, 11, 23
33 Recommendations 2 weeks 2, 11, 23
34 Study Submission 1 week 2, 11, 23, 32, 33
35 Presentation of the Result 1 week 2, 11, 23, 32, 33
36 Evaluation Meeting 1 week 2, 11, 23, 32, 33

Keys = Slack Time Ancilliary Proccess

Figure 1 – Study Project Gantt Chart (Own Figure)

 74109683_ R1901D7421833 Page 25 of 41

4.0 Contribution:

Following the survey of the procedures and methods involved in the research study, the

answers to how individual methods contributes to the objective of the study are explained

comprehensively in this chapter, which includes the recognition of the condition and the

total display of all the requirements for executing and programming of the mobile B2B

software application. Evidence derived from software case studies and organization are

incorporated together with the knowledge researchers have gotten while investigating a

specific method.

This chapter will in details discuss about the result derived carefully from a similar

occurrence that has already been carried out especially those that has the same

characteristics, organizational research, this will greatly assist in providing clear evidence

on the effectiveness of the highlighted procedures on the research study goals. The client

will have an explicit explanation of the requirements to carry out the project, and thereby

decide if he/she can carry out the project or take the option of outsourcing based on the

emanating results from the functional, structural and resource requirement displayed.

Nevertheless, if the research study indicates that carrying out the project holistically is

within the capacity of the client, then, the first stage of the requirement and project

planning elicitation phase is already achieved, thereby economizing money and time for the

client.
 74109683_ R1901D7421833 Page 26 of 41

4.1 Functional Requirement:

4.1.1 Stakeholder Analysis

Pacheco and Garcia (2012) states that the recognition and apprehension of stakeholders is

essential or important for the requirement evocation procedures and for the following

classification of the software program in terms of quality. The software can only

accomplish its expected requirements only if the relevant stakeholders can be identified

(Babar et al., 2015). Using a stakeholder analysis strategy to an organization which has

already initiated an e-procurement system, a researcher, Pan (2005) states that it is

important to understand the stakeholders and their various goals in order to prevent the

neglect of the data systems development projects. According to Kaur and Sengupta (2011),

the absence of the client’s involvement in the information technology projects can cause

the need for allegiance and refusal of project support which are very essential if the project

must come out successful.

Research study shows that stakeholder’s analysis is solidly associated to the risk

identification and analysis procedure because of the accompanying issues, especially when

paying no attention to what the stakeholder wants before venturing into software project

(Vrhovec et al., 2015). In scenarios which occurs in a banking sector, where we have

research findings that are totally centered on application development, they tend to go

straight to fish out that it is of utmost important that there should be a proper dialogue

between the stakeholders and for the most part, a good understanding of the information

technology’s personnel discussing the most suitable way for the business procedures. The

impact of the stakeholder towards project risks and hazards cannot be overemphasized,

according to Rost and Glass (2009), highlighting the importance of evaluation and total
 74109683_ R1901D7421833 Page 27 of 41

checkmate on the project hazards. Due to the exploration of the end users, software

engineer programmers and customers, an industrious control stakeholder analysis in an

interconnection with software benchmarking makes a merchandised analysis unnecessary.

4.1.2 Software Benchmarking

In reality, there are lots of software producers who has so far presented the mobile B2B

software applications for different companies and organizational sections, and this implies

that software benchmarking analysis completely comes up with ideas of showing the

different abilities that are needed and quite suitable for an organization (Tornack et al.,

2011). In general, mobile B2B software application should be constantly modified and

inspected in order to bring out its best features and assist industries to achieve its maximum

height in market competition (Ojala and Tyrväinen, 2008), for example, in the drug

industry.

Furthermore, according to Maire et al., (2005) in reference to its implementation in france,

it was discovered that 50% of the carefully inspected organizations, selectively use

benchmarking daily, and this is done to discover the foremost operations, with the goal of

achieving am improvement in the information technology procedures. According to Pang et

al (2009), The implementation of benchmarking practically and conceptually on the

prerequisites elicitation procedures of a project development website shows that in order to

investigate the information technology tool-centered prerequisites, the use of benchmarking

is of outmost important. Loo (2003) successfully implements benchmarking in the factors

 74109683_ R1901D7421833 Page 28 of 41

of the project management as a technical characteristics for demonstrating the fitness of

benchmarking for big projects.

In certain circumstances, involved in project management, the application of benchmarking

can only be fortunate for scientific aspects, and this demonstrates the fitness of

benchmarking for multiplex projects (Loo, 2003). Mostly concerning the motives of

disclosing the functional requirements of the client mobile B2B software application,

benchmarking is the position to give important industry knowledge of an already existing

and acquired software application. This replaces the space created between the functional

requirement that has already been spotted out in the analysis of the stakeholder and the

functional requirements that are essential for the actual execution

4.2 Structural Analysis

4.2.1 System Environment Analysis

Concerning the system environmental analysis, it has been recorded that the analysis is

centered on its ability to asses few of the component that gives rise to the introduction of

new techniques which involves certain problems in relation to new system requirements,

while still under observation from the point of view of the innovation system (Huselid. M.

A. et al., 2005). Therefore, there is a popular knowledge that information technology

environment needs an exclusive skill, which are set aside to be able to prevent

opportunities for failures. Programming of software on a bigger scale and also on a lengthy

period of time will be examined majorly, and importantly, it will help in the general

conclusion of expertise requirement of the workforce as well as their essential threats.

 74109683_ R1901D7421833 Page 29 of 41

According to Charrette (2005) inadequate adaptation and problematic information

technology services greatly contributed to a large extent for the several failures that were

recorded in the programming of software projects of big and small industries. Those

challenges can result to foregone gains which can be put to a stop by an engrossed analysis

of the information technology edifice of the client.

Furthermore, requirements needed from the risk management, information technology

security and service management are derived from the system environment analysis, which

permits further closure, and this is assisted by the case of a Greek software organization

carrying out the execution of project at the client’s request (Maroukian, 2010). The

information technology support’s major role for the consumers, and on the flip side,

additional development in the other direction is a comprehensive based study. This

therefore corresponds with the already presented procedure, which brings about the system

environmental analysis to be the base for continuous personnel analysis (Byrd and Turner,

2000).

4.2.2 Personnel Analysis

There is high suggestion for the use of personnel analysis since it is a multiple intensive

responsibility for the execution, programming and maintenance of the software, not just for

the programmers, but also the project managers, maintenance, management workforce and,

tester staff (Barreto et al., 2008).

Henceforth, to show the personnel requirement that the client has to encounter, our

attention should be solidly on the analysis. According to Firesmith (2004), case-based

 74109683_ R1901D7421833 Page 30 of 41

requirement evocation procedure pays attention to the scope and therefore staffing needed.

Kirkor (2010) concluded that qualified staffs should be evenly allocated to various areas of

the organization to ensure that there is a fortunate and successful execution of the

procedure for the mobile software development. Therefore, the conclusion that follows the

subcontract work or carry out the reformation on the grounds that the chance to undergo a

successful training on the spot user and administration which also includes accepting help

when needed, these are extra gains of personnel analysis and also outlying skills wants.

Following the statement of Dave and David (2012) the nominated personnel that oversees

that the records are adequately registered in order, and also remain constant till the

executions are carried out, after so much inspection must have taken place, especially new

functions that has been implemented are efficient workforce of the organization whose

daily assignment includes; designs, administrators, programmers, testers, managers and

maintenance personnel, on a steady basis, assistance are carried out and also the system

upgrade that has been installed are always in check for efficiency. In association with the

above, there should be adequate supply of workforce by company Y, and a good

scrutinizing of the requirements evocation are suggested by Holuram (2013), and this

brought forth the importance that was discovered during the case study.

The allocation of human resources and planning especially when it involves developers

during software project to certain responsibility and task shows an importance in handling

the estimated workload per employee and time issues (Park et al., 2015). Therefore

attainable occurrence of congestion will be easily identified before they occur.

 74109683_ R1901D7421833 Page 31 of 41

The client should consider personnel analysis as a basic step so as to decide whether hiring

an external contractor or outsourcing the project may be an actual possibility. Contractors

can be a good replacement in situation where we have issues of small proficiency spaces,

and they can fit into those spaces with so much ease. (Wu and Zmud, 2010)

Company Y must be able to scrutinize this process to get qualified and certified employees

who can deliver the critical process of setting up a complementary software for the desired

objective of this project. Other staff to be picked should be at least trainable because

training is inevitable for this IT service provider services such as the mobile B2B software

application

4.5 Risk Identification and Analysis

Risk identification and analysis is particularly important for client that intend to venture

into an unknown area with a new products because the risk involved is highly susceptible

in IT projects (Lock, 2013). Analysis and identification of risk is important so as to

categorize the detailed requirement and to evaluate whether the client will be able to

control the risks involved without any assistance. There are many case studies that

elaborate this fact: The government sector in Barbados applied a holistic risk management

frame work for a software engineering project, Dey et al. (2007) explains that risk

identification and analysis discovered at the initial stages of the software project represents

a prerequisite to guarantee an understandable risk apprehension and understanding that may

lead to the immediate measures to be taken to put the risks under control.
 74109683_ R1901D7421833 Page 32 of 41

When a leading IT professionals interviewed Baccarini et al., (2004), they stated that huge

risk are associated with IT projects especially in terms of the budget, personnel and

scheduling activities. The methodology introduced considers this fact in regards to the

execution of overlying risks and hazards. Furthermore, (Baccarini et al., 2004, p. 286)

stated that instances of incidents that occurred during the “London Stock Exchange’s

Transfer and Automated Registration of Uncertified Stock (TARUS) system” and that of

the “American Airlines Information Services (AMRIS)” which recorded so many

unsuccessful information technology projects are said to be related to inadequate

management of risks and hazards. Therefore, it is paramount that the client is given the

appropriate knowledge summary regarding the hazards and risks involved during the

process, and get a first class preventive measures which can be applied so as to assess the

ability the organization can provide in taking control of risk.

4.3 Resource Requirement

4.3.1 Project Time Planning

Project time planning plays an important function for organization because of the presence

of so many challenges that happened with time; congestion and guessing of wrong time

leads to time constraints and delivers behind schedule, which negatively affect the cost of

the project (Hazzan and Dubinsky, 2007). In an attempt to illustrate the need for a suitable

project planning method for a proper time estimation for a provisional requirement,

Charette (2005) provided several examples of failed IT projects. Scheduling is a great step
 74109683_ R1901D7421833 Page 33 of 41

to avoid variabilities in project time planning, since information technology project

estimation is not an exact science.

In an attempt to examine the adoption of time planning strategies for software projects,

Verner et al., (2007) discovered that the uncooperative time arrangement coupled with the

insufficient prerequisites engineering are too poor for consumption, and that was why

scrutinizing the assumption of time planning proposal were selected, and this is causing the

increment of time risks or hazards, and also resulted to the numerous unsuccessful projects

in the past life. Therefore, error in time evaluation, related losses and occurring hazards

which the client can experience can be avoided using an intended analysis with an

appropriate time approximation.

4.3.2 Life-Cycle Cost Analysis

According to Passenheim, (2009) the requirements needed for the project, the major cause

that prevents execution are cost. Vlachy (2014) states that Life Cycle Cost when applied

during an engineering project shows that LCC is a very extensive and specific method in

respect to evaluating the firm’s product cost until the life span of such product has elapsed,

especially when the method is already incorporated into the product origination stage. A

major privilege of the technique can be seen in strategic decision making due to the

assistance of LCC. The benefit of the intentional execution corresponds: Between the

displayed procedures, it becomes feasible to acquire important prudent conclusion for the

accomplishment of the project, but this can only be achievable if the organization can

provide the required resources.

 74109683_ R1901D7421833 Page 34 of 41

Before the life cycle cost analysis could ascertain a validation, a proper and interrogating

research study should be carried out, according to Korpi and Ala-Risku (2008) the life

cycle cost analysis has been widely known due to the explained necessity of its long-term

affordability, and this makes it ranked above other cost estimation methods. Furthermore,

concealed costs that are unpredictable in software projects are revealed by life cycle cot

analysis (Chifosky and Cross, 1990). Now, this is particularly important for organizations

that have little or no IT basis and therefore lack software for the cost estimation.

5.0 Concluding Remarks

In general, a comprehensive proposal which includes various types of project requirements

that has proven to be authentic is being presented, which the client already has developed a

special interest. The widely accepted method is the comprehensive proposal, on the

grounds that it provides a complete format for application, and in another way, it proffers

information that can assist in identifying attainable complications. The introduced

comprehensive proposal has been modified to solve a particular case for the client and its

specific demands which is majorly to help in distribution of drugs from manufacturer to the

distributor, and this study will bring so much satisfaction to the client’s needs. The

previous software engineering project that encountered different incidents shows the

acceptability and rationality of its method to look into the initiated plans, and therefore, the

client’s various demands of daring into programming of a mobile B2B software application

for company Y. In the scenario where we there is need for change or improvement on the

client’s demands, the adjacent dialogues or continuous communication that were

established with the client during the course of the study will enable the client to have
 74109683_ R1901D7421833 Page 35 of 41

maximum and accurate information. Additionally, the client will be able to recognize each

step and activity during the project with the help of the Gantt-chart.

The purpose of the study was to show the list of prerequisites needed, to have a

comprehensive creation of the software application needed for business-2-business (B2B)

transaction for company Y, and these requirements involves basic functional, financial,

non-financial, and structural resources. After the submission of the final report, the client

makes a final decision based on the result of the conducted analysis contained in the

submitted report. In the final decision making, it solely rests on the client to either go ahead

with the programing of the software and implement, or rather make an outright purchase of

a software that meets his/her demand (“build or buy”) (Cortellessa et al., 2008), or to

disembark from the software project.

The results of the conducted analysis will be able to guide the client on all the resources

he/she needs to provide to be able to carry out the project. If the client is capable to provide

all necessary requirement and makes a decision, whatever decision that is made stands.
 74109683_ R1901D7421833 Page 36 of 41

References

Al-Naeem, T., Rabhi, F.A., Benatallah, B. and Ray, P.K. (2005) “Systematic Approaches
for Designing B2B Applications”, International Journal of Electronic Commerce, 9
(2), pp. 41-70.
Babar M.I., Ghazali M., Jawawi D.N.A. and Zaheer, K.B. (2015) “StakeMeter: Value-
Based Stakeholder Identification and Quantification Framework for Value-Based
Software Systems”, PLoS ONE, 10 (3), pp. 1-33.
Baccarini, D., Salm, G. and Love, P.E.D. (2004) “Management of risks in information
technology projects”, Industrial Management & Data Systems, 104 (4), pp. 286-295.
Bagozzi, R. P. (2009) ‘Marketing as an organized behavioral system of exchange’, Journal
of Marketing, 38 (4), pp. 77–81.
Barreto, A., Barros, M. and Werner, C.M.L. (2008) “Staffing a software project: A
constraint satisfaction and optimization-based approach”, Computers & Operations
Research, 35, pp. 3073-3089.
Bedell C. (2013) Mobile apps development: Defining requirements is a whole new
ballgame. [Online]. Available at:
https://searchsoftwarequality.techtarget.com/feature/Mobile-apps-development-
Defining-requirements-is-a-whole-new-ballgame (Accessed on 18 August, 2021)
Bhattacharya, C. B., & Korschun, D. (2008) ‘Stakeholder marketing: Beyond the four Ps
and the customer’, Journal of Public Policy & Marketing, 27 (1), pp. 113–116.
Byrd, T.A. and Turner, D.E. (2000) “Measuring the Flexibility of Information Technology
Infrastructure: Exploratory Analysis of a Construct”, Journal of Management
Information Systems, 17 (1), pp. 167-208.
Calvert S. (1995) “Managing stakeholders”, in: Turner, J.R. (ed.), The commercial project
manager. Maidenhead: McGraw-Hill, pp. 214-222.
Charette, R.N. (2005) “Why Software Fails”, IEEE Spectrum [Online]. Available at:
http://spectrum.ieee.org/computing/software/why-software-fails (Accessed on 7
August, 2021).
Chikofsky, E.J. and Cross, J.H. (1990) “Reverse Engineering and Design Recovery: A
Taxonomy”, IEEE Software, 7 (1), pp. 13-17.
Cortellessa, V., Marinellia, F. and Potena, P. (2008) “An optimization framework for
“build-or-buy” decisions in software architecture”, Computers & Operations
Research, 35, pp. 3090-3106.
Dahlstrom, E., Brooks, D.C., Grajek, S. and Reeves, J. (2015) ECAR Study of Students
and Information Technology, 2015, ECAR, Louisville, CO, p. 47. Available online
at: Google Scholar (Accessed on 7 August, 2021)
 74109683_ R1901D7421833 Page 37 of 41

Daniel A. (2016) 5 Effective Uses of Mobile Technology In The Classroom. Available

online from: https://elearningindustry.com/5-uses-mobile-technology-in-the-
classroom (Accessed on 9 August, 2021)
Dave B. and David T.B. (2018) Chapter 10: Information Systems Development. [Online].
Available at: https://bus206.pressbooks.com/chapter/chapter-10-information-
systems-development/ (Accessed on 13 August, 2021).
Dey, P.K., Kinch, J. and Ogunlana, S.O. (2007) “Managing risk in software development
projects: a case study”, Industrial Management & Data Systems, 107 (2), pp. 284-
303.
Dvir, D., Raz, T. and Shenhar, A.J. (2003) “An empirical analysis of the relationship
between project planning and project success”, International Journal of Project
Management, 21, pp. 89-95.
Eckardt, J.R., Davis, T.L., Stern, R.A., Wong, C.S., Marymee, R.K. and Bedjanian, A.L.
(2014) “The Path to Software Cost Control”, Defense AT&L, November–December
2014, pp. 23-27.
Firesmith, D.G. (2004) “Creating a Project-Specific Requirements Engineering Process”,
Journal of Object Technology, 3 (5), pp. 31-44.
Glinz, M. and Wieringa, R.J. (2007) “Stakeholders in Requirements Engineering”, IEEE
Software, 28, pp. 18-20.
Hazzan, O. and Dubinsky, Y. (2007) “The Software Engineering Timeline: A Time
Management Perspective”, IEEE International Conference on Software – Science,
Technology and Engineering, pp. 95-103.
Higham, A., Fortune, C. and James, H. (2015) “Life cycle costing: evaluating its use in UK
practice”, Structural Survey, 33 (1), pp. 73-87.
Hines, P. (1998) “Benchmarking Toyota’s supply chain: Japan vs UK”, Long Range
Planning, 31 (6), pp. 911-918.
Houdek, F. and Pohl, K. (2000) “Analyzing requirements engineering processes: A case
study”, Proc. of the 11th International Workshop on Database and Expert Systems
Applications (DEXA’00), pp. 983-987.
Huselid, M. A., Becker, B. E., & Beatty, R. W. (2005) The workforce scorecard:
Managing
Jepsen, A.L. and Eskerod, P. (2009) “Stakeholder analysis in projects: Challenges in using
current guidelines in the real world”, International Journal of Project Management,
27, pp. 335-343.
Jucan, G. (2013) “People in Senior Project Roles”, in: Lock, D. and Scott, L. (eds.), The
Gower Handbook of People in Project Management. Farnham: Gower.
 74109683_ R1901D7421833 Page 38 of 41

Kapp, M.J. and Girmscheid, G. (2005) “Risk based life cycle cost analysis model for
comparable life cycle project delivery decision taking”, in: Collaboration and
Harmonization in Creative Systems. London: Taylor & Francis, pp. 895-901.
Kaur, R. and Sengupta, J. (2011) “Software Process Models and Analysis on Failure of
Software Development Projects”, International Journal of Scientific & Engineering
Research, 2 (2), pp. 1-4.
Kodali, G.A.R. (2008) “Benchmarking the benchmarking models”, Benchmarking: An
International Journal, 15 (3), pp. 257-291.
Kogdenko, V.G. (2011) Analysis of personnel in the system of value-oriented management.
The Economic Analysis: Theory and Practice, 2 (209), pp. 121-129.
Korpi, E. and Ala-Risku, T. (2008) “Life cycle costing: a review of published case studies”,
Managerial Auditing Journal, 23 (3), pp. 240-261.
Krikor, M. (2010) “IT Project Environment Factors Affecting Requirements Analysis in
Service Provisioning for the Greek Banking Sector”, Journal of Software
Engineering & Applications, 3, pp. 858-868. Available at: 10.4236/jsea.2010.39100
(Accessed on 22 August, 2021).
Lindholm, A. and Suomala, P. (2005) “Learning by costing: sharpening cost image through
life cycle costing?”, 7th Manufacturing Accounting Research Conference, Tampere,
Finland, 30.May – 1.June.
Liu B. et al. (2016) Structural Analysis of User Choices for Mobile App Recommendation
[Online]. Available at: https://arxiv.org/abs/1605.07980 (Accessed on 15 August,
2021)
Lock, D. (2013) Project Management. 10th ed., Farnham: Gower Publishing Ltd.
Loo, R. (2003) “A multi-level causal model for best practices in project management”,
Benchmarking: An International Journal, 10 (1), pp. 29-36.
MacLean, R., Stepney, S., Smith, S., Tordoff, N., Gradwell, D., Hoverd, T. and Katz, S.
(2004) Analysing Systems: determining requirements for object oriented
development. Hemel Hempstead: Prentice Hall International.
Madden, T. J., Fehle, F., & Fournier, S. (2006) ‘Brands matter: An empirical demonstration
of the creation of shareholder value through branding’, Journal of the Academy of
Marketing Science, 34 (2), pp. 224–235.
Maire, J.-L., Bronet, V. and France, A. (2005) “A typology of best practices for a
benchmarking process”, Benchmarking: An International Journal, 12 (1), pp. 45-60.
Maley, C.H. (2012) Project management concepts, methods, and techniques. Boca Raton,
Fla.: CRC Press.
 74109683_ R1901D7421833 Page 39 of 41

Maroukian, K. (2010) “IT Project Environment Factors Affecting Requirements Analysis

in Service Provisioning for the Greek Banking Sector”, Journal of Software
Engineering & Applications, 3, pp. 858-868.
MindFit Consulting (2018) Personnel analysis. [Online]. Available at:
https://www.mindfitconsulting.com/en/personnelanalysis/ (Accessed on 20 August,
2021)
Nakatani, T., Hori, S., Katamine, K., Tsuda, M. and Tsumaki, T. (2014) “Estimation of the
Maturation Type of Requirements from Their Accessibility and Stability”, IEICE
Transactions on Information and Systems, 97 (5), pp. 1039-1048.
Newcombe, R. (2003) “From Client to Project Stakeholders: A Stakeholder Mapping
Approach”, Construction Management and Economics, 21, pp. 841-848.
Nicholas, J.M. and Steyn H. (2012) Project management for engineering, business and
technology. 4th ed., London: Routledge.
OECD (2004) "ICT, E-Business and Small and Medium Enterprises", OECD Digital
Economy Papers, No. 86, OECD Publishing,
Paris, https://doi.org/10.1787/232556551425 (Accessed on 7 August, 2021)
OECD (2004) “ICT, E-Business and Small and Medium Enterprises”, OECD Digital
Economy Papers, No. 86, OECD Publishing, Paris.
http://dx.doi.org/10.1787/232556551425 (Accessed on 7 August, 2021)
Ojala, A. and Tyrväinen, P. (2008) “Best practices in the Japanese software market”,
Global Business & Organizational Excellence, 27 (2), pp. 52-64.
Otero, L.D., Centeno, G., Ruiz-Torres, A.J. and Otero, C.E. (2009) “A systematic approach
for resource allocation in software projects”, Computers & Industrial Engineering,
56, pp. 1333-1339.
Pacheco, C. and Garcia, I. (2012) “A systematic literature review of stakeholder
identification methods in requirements elicitation”, The Journal of Systems and
Software, 85, pp. 2171-2181.
Pan, G.S.C. (2005) “Information systems project abandonment: a stakeholder analysis”,
International Journal of Information Management, 25, pp. 173-184.
Pang, M.-S., Suh, W., Kim, J. and Lee, H. (2009), “A Benchmarking-Based Requirement
Analysis Methodology for Improving Web Sites”, International Journal of
Electronic Commerce, 13 (3), pp. 119-162.
Park, J., Seo, D., Hong, G., Shin, D., Hwa, J. and Bae, D.-H. (2015) “Human Resource
Allocation in Software Project with Practical Considerations”, International Journal
of Software Engineering and Knowledge Engineering, 25 (1), pp. 5-26.
Passenheim, O. (2009) Project Management. Copenhagen: Bookboon.
 74109683_ R1901D7421833 Page 40 of 41

Pizzutillo P. (2015) Software Benchmarks and Benchmarking. [Online]. Available from:

https://www.castsoftware.com/blog/software-benchmarks-and-benchmarking
(Accessed on 7 August, 2021)
Pouloudi, A. and Whitley, E.A. (1997) “Stakeholder identification in inter-organizational
systems: gaining insights for drug use”, European Journal of Information Systems, 6
(1), pp. 1-14.
Power, K. (2010) “Stakeholder Identification in Agile Software Product Development
Organizations”, Agile Conference, August 2010, pp. 87-94.
Pries, K.M. and Quigley, J.M. (2008) Project Management of Complex and Embedded
Systems Ensuring Product Integrity and Program Quality. Hoboken: Taylor and
Francis.
Project Management Institute (2013) “A Guide to the Project Management Body of
Knowledge (PMBOK Guide)”, Newtown Square, Pa.: Project Management Institute.
Rost, J. and Glass, R.L. (2009) “The Impact of Subversive Stakeholders on Software
Projects”, Communications of the ACM, 52 (7), pp. 135-138.
Sadler K., Robertson T. & Kan M. (2005) Use Scenarios: A Useful Design Tool For
mBusiness. [Online]. Available at:
https://www.researchgate.net/publication/4167674_Use_scenarios_A_useful_design
_tool_for_mBusiness (Accessed on 8 August, 2021)
Sharp, H., Finkelstein, A. and Galal, G. (1999) “Stakeholder identification in the
requirements engineering process”, Proceedings of 10th International Workshop on
Database & Expert Systems Applications (DEXA), pp. 387-391.
Smilansky, O. (2015) “Third-Party Power: The Rise of the B2B App Store”, CRM
Magazine, 19 (11), pp. 28-31.
Tornack, C., Christmann, S. and Hagenhoff, S. (2011) “Tendenzielle Unterschiede
zwischen B2B und B2C-Anwendungen für mobile Endgeräte”, University of
Goettingen, Chair of Application Systems and E-Business, Working Paper No.
3/2011.
Van Aardenne, J. (2002) Uncertainties in emission inventories, PhD thesis Wageningen
University, The Netherlands.
Vargo, S. L., & Lusch, R. F. (2004) Evolving to a new dominant logic for marketing,
Journal of Marketing, 68, 1–17.
Verner, J.M., Evanco, W.M. and Cerpa, N. (2007) “State of the practice: An exploratory
analysis of schedule estimation and software project success prediction”,
Information and Software Technology, 49, pp. 181-193.

Veronica et al. (2014) “Requirement analysis method of ecommerce websites development

for small-medium enterprises, Case Study: Indonesia”, International Journal of
Software Engineering & Applications (IJSEA), 5 (2).
 74109683_ R1901D7421833 Page 41 of 41

Vlachý, J. (2014) “Using Life Cycle Costing for Product Management”, Management, 19
(2), pp. 205-218.
Vrhovec S.L.R., Hovelja, T., Vavpotič, D. and Krisper, M. (2015) “Diagnosing
organizational risks in software projects: Stakeholder resistance”, International
Journal of Project Management, 33, pp. 1262-1273.
Watson, G.H. (1993) Strategic Benchmarking: How to Rate Your Company’s Performance
Against the World’s Best. New York: Wiley.
Wu, W.W. and Zmud, R.W. (2010) “Facing the Challenges of Temporary External IS
Project Personnel”, MIS Quarterly Executive, 9 (1), pp.13-21.
Zamfiroiu, A. (2015) “Factors Influencing the Quality of Mobile Applications”,
Informatica Economică, 18 (1), pp. 131-138.
Zhang, Y. and Bishop, C. (2013) “Project-Management Tools for Libraries: A Planning
and Implementation Model Using Microsoft Project 2000”, Information Technology
and Libraries, 24 (3), pp. 147-152.
Zobel, T., Almroth, C., Bresky, J., Burman, J., (2003) ‘The Identification and assessment of
environmental aspects in an EMS context: an approach to a new reproducible
method based on LCA methodology’, Journal of Cleaner Production, 10, pp. 381-
396.
Zowghi D. and Coulin C. (2005) “Requirements Elicitation: A Survey of Techniques,
Approaches, and Tools”, in: Engineering and Managing Software Requirements.
Berlin: Springer, pp. 19-46.