3 (2) 131-141

See discussions, stats, and author profiles for this publication at: https://www.researchgate.
net/publication/327362548
A Cost Effective Approach to Develop Mid-size Enterprise Software Adopted

the Waterfall Model
Article · September 2018
CITATION READS
1 24
1 author:
Mohammad Nehal Hasnine

Kyoto University
8 PUBLICATIONS 3 CITATIONS
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
Information Infrastructure for Supporting Education and Learning by using Educational Big Data View project
Appropriate Image Recommendation for Vocabulary Learning using Educational Big Data and Image Analysis View project
All content following this page was uploaded by Mohammad Nehal Hasnine on 01 September 2018.
The user has requested enhancement of the downloaded file.

World Academy of Science, Engineering and Technology
International Journal of Computer and Information Engineering
Vol:9, No:5, 2015
A Cost Effective Approach to Develop Mid-size

Enterprise Software Adopted the Waterfall Model
M. N. Hasnine, M. K. H. Chayon, M. M. Rahman
dissemination, and acquisition of data. Due to these facts,

Abstract—Organizational tendencies towards computer-based end-user application development has become a dominant force
information processing have been observed noticeably in the in many organizations [2]. Therefore, numerous kinds of tools,
third-world countries. Many enterprises are taking major initiatives techniques, and approaches have been tested in the
towards computerized working environment because of massive development of enterprise software. However, limited budgets,
benefits of computer-based information processing. However,
designing and developing information resource management software a strict deadline, and inadequate IT-knowledge of the end-users
International Science Index, Computer and Information Engineering Vol:9, No:5, 2015 waset.org/Publication/10001384
for small and mid-size enterprises under budget costs and strict remain the big challenge for IT analysts and software
deadline is always challenging for software engineers. Therefore, we engineers.
introduced an approach to design mid-size enterprise software by System analysis and design are an exciting and active field
using the Waterfall model, which is one of the SDLC (Software where analysts continually learn new techniques and
Development Life Cycles), in a cost effective way. To fulfill research approaches to developing systems more effectively and
objectives, in this study, we developed mid-sized enterprise software
named “BSK Management System” that assists enterprise software efficiently [3]. Several approaches, methodologies, and
clients with information resource management and perform complex techniques have been reported and tested in the process of
organizational tasks. Waterfall model phases have been applied to software analysis. However, two widely used methodologies
ensure that all functions, user requirements, strategic goals, and are: 1) Software Development Life Cycle (SDLC) and 2)
objectives are met. In addition, Rich Picture, Structured English, and Prototyping [4]. In IT project management, SDLC process
Data Dictionary have been implemented and investigated properly in applies to information system development to ensure that all
engineering manner. Furthermore, an assessment survey with 20
participants has been conducted to investigate the usability and functions, user requirements, strategic goals, and objectives are
performance of the proposed software. The survey results indicated met. The SDLC provides a structured and standardized process
that our system featured simple interfaces, easy operation and for all phases of any system development effort. In this
maintenance, quick processing, and reliable and accurate transactions. particular study, the Waterfall approach, which is one of
SDLCs, has been considered as the software development
Keywords—End-user Application Development, Enterprise methodology.
Software Design, Information Resource Management, Usability. The rest of this article is structured as follows. A brief
introduction to SDLCs and particularly Waterfall approach had
I. INTRODUCTION been articulated in Section II. Section III covers the articles that
T HE processes to develop computer-based information

systems have been changed significantly in recent years
[1]. As mentioned earlier, organizational tendencies towards
have been reviewed. An introduction to the approach used to
develop BSK Management System has been articulated in
Section IV. Next Section V discusses on the technological
ICT-based information processing have been observed specifications involved in this study and the outline of the
noticeably in many third-world countries. In last decade, many system. The following Section VI concisely discusses on the
small-sized and mid-sized companies have taken initiatives to usability test conducted to support this study including the
switch to computerized working environment. Computer-based procedures and results. Finally, Section VII summarizes the
information management not only merits by saving time, but outcome of this study, and finally recommends some future
also helps the employee to perform complex tasks. Other works in Section VIII.
benefits of computer-based information processing over
manual-processing are record, organization, retrieval, display, II. SDLCS & WATERFALL MODEL
The SDLC models particularly in software development
M. N. Hasnine is a full-time PhD student with the Graduate School of
allow analysts to draw and design systems beyond traditional
Engineering, Tokyo University of Agriculture and Technology, Nakacho technological boundaries. In the development of enterprise
2-24-16, Koganei, Tokyo 184-8588, Japan (phone: +81-80-4919-4030; fax: software, the SDLC has drawn heavy attention for
+81-042-385-9747, e-mail: [email protected],
[email protected]).
cost-efficient, effective, and high-quality product development.
M. K. H. Chayon is currently working with Millennium Certis Security It can also be mentioned that a software lifecycle covers all the
Bangladesh Ltd., House#123, Block-E Road No 19/A. (e-mail: stages from its inception with requirement gathering through to
[email protected]). maintenance. IT analysts heavily rely on SDLC methodologies
M. M. Rahman is working with the Kiwibank, 139 Kelburn Parade,
Kelburn, Wellington 6012 (e-mail: [email protected]). to ensure that all functions, user requirements, strategic goals,
M. N. Hasnine, M. K. H. Chayon & M. M. Rahman was with the and objectives are met. As stated earlier, the SDLC provides a
Department of Computer Science and Engineering, Stamford University structured and standardized process for all phases of any system
Bangladesh, 51 Shiddheswari Rd, Dhaka-1217, Bangladesh.
International Scholarly and Scientific Research & Innovation 9(5) 2015 1182 scholar.waset.org/1307-6892/10001384
Vol:9, No:5, 2015
development effort. However, to our best understanding, not significant amount

SDLC models can be categorized as falling under three of researches have been published yet which emphasized on the
broad categories: 1) linear, 2) iterative, and 3) a combination of software design in cost effective ways. Therefore, in this study
linear and iterative models [5]. Ruparelia also included that we introduced an approach to developing small-sized and/or
based on the existence and gained popularities, the Waterfall, mid-sized enterprise software at a budget cost. Our proposed
B-Model, Incremental Model, V-Model, Spiral Model, system will also assist software engineering students, young
Wheel-and-Spoke Model, and Unified Process Models are used software engineers, and IT analysts to understand the phases
widely. involved in the Waterfall model effectively. Moreover, our
The Waterfall model was firstly documented by Benington proposed method will help software engineers to understand
[6] and modified lately by Winston Royce [7] in 1970. This how to develop software under a strict deadline.
model has underpinned all other models since it created a firm
foundation for requirements to be defined and analyzed prior to IV. THE APPROACH
any design or development [5]. Phases in Waterfall model This section briefly describes the approach followed to
historically included the following with the key focus on design the software.
parentheses: feasibility (readiness), analysis (what), design
(how), detailed to design (how), coding and unit testing A. In-a-Nutshell

(technology), testing (correctness), and implementation A non-profitable organization located in Bangladesh had
(transition to operation) [8]. been selected to implement our proposed approach. The
To our best understanding, the Waterfall model may be the organization is involved in activities like to promote reading
best to use when developing an enterprise relational database. habits, enlightenment, and progressive ideas among students
In addition, the Waterfall model provides benefits over other and the general public in Bangladesh. For the sake of
models by providing back-end functionalities, user friendly confidentiality, this article does not reveal the company name
data representation, easy to implement, easy to manage due to and certain operations. In this study, the term ‘BSK’ is used as a
rigidity of the model, less possibilities of phase overlapping, pseudonym to represent the organization. It can be mentioned
works well for small size projects, and cost effective. In that the system design and implementation phases have been
addition, the comparative study by [9] indicates that the pros of done based on the given information by the organization.
this model dominate over other SDLC models. Therefore, we In this project, we have used the Waterfall model because
have considered the Waterfall model to design software. this model allows analysts to draw and design systems beyond
However, [10] scrutinized some of the common confusions that traditional technological boundaries. We have followed a
analysts often experience while working with the Waterfall generic Waterfall model where all steps are iterative. Fig. 1
model. shows the iterative feedback approach used to design our
system.
III. LITERATURE REVIEW Preliminary investigation and interviewing employees
Research related to techniques, methodologies, and regarding opportunities and problems in the organization have
approaches has been well investigated and documented in the been taken into account as Requirement Gathering Phase. In
literature. A large number of comparative and empirical studies the System Analysis Phase, 4-main analyses which are 1)
can be found in the literature. However, not many studies have Problem 2) Requirement 3) Decision and 4) Feasibility had
been published for students to understand the processes of the been analyzed. While into System Implementation (Design)
Waterfall model. Therefore, this article targets software Phase, technical architecture, system standard, and technical
engineering students and IT analysts to understand the phases specifications have been put into action. Coding, Testing,
involved in the Waterfall model effectively. Conversion, and Maintenance phases have been executed
At the beginning of our study, we have investigated the depending on the requirements of the user.
failures and risks involved in software development. Empirical The proposed system purposed to assist current employees of
study conducted by [11] investigated some major reasons the organization with their information resource management
behind information systems failure in developing countries. in a cost effective way.
The investigation concluded that Design-Acuity gaps are the At first, Data Flow Diagram (DFD) of three levels of the
main reasons behind many information system failures in organization including Context Level DFD, System Level
developing countries. Besides, various attributes (such as DFD, and Level-1 DFD have been designed and documented.
project control, ease of use, and communicability) associated Then we analyzed the Level-1 DFD into different subsystems.
with methodologies might cause full or partial system failure. After that, we have drawn the Rich Picture depending on the
In addition, the empirical study conducted by [12] revealed that organization’s different activities. The Entity Relationship
a large gap observed between the definition of project success Diagram (ERD), the Data Dictionary based on various
defined by software engineers and the popular definition in the databases, Entity Life Cycle Diagram, and Structured English
society. have been designed and documented respectively.
Chen [13] implemented a preliminary framework for
classifying entity-relationship models and discussed how these
models might be translated from one to the other.
Vol:9, No:5, 2015
C. System Analysis & Design

DFDs have been drawn prior to system implementation.
DFD is considered as a graphical representation to illustrate
details of data flows and functions. Chun [14] articulated some
characteristics of DFDs as 1) it supports analysis and
requirement stages of system design, 2) diagramming
technique with annotation, 3) describes a network of
activities/processes of the target system, and 4) allows for
behaviors of parallel and asynchronous; and 5) stepwise
refinement through hierarchical decomposition of process.
Context Level DFD, System Level DFD, and Level-1 DFD
have been drawn as a part of system analysis in BSK
Management System. Figs. 2-4 display the Context Level DFD,
the System Level DFD, and the Level-1 DFD of BSK
Management System respectively.
Fig. 1 Waterfall model with iterative feedback

B. Requirement Gathering
Requirement gathering (synonymously data collection) was
the initial phase. The non-profitable organization we have
developed the software for, is working actively with the
motivation to enlighten people. The organization receives
donation as a source of fund, to maintain their organizational
expenses. The organization’s operation can be mentioned
as-student enrollment, the program progress, examination
handling, donor handling, book purchasing, publications, and
book supplying. To determine the functional requirements,
employees in various positions have been interviewed.
Received data have been well analyzed and our investigation
concludes that the organization requires 9-different modules to
run their basic operation.
As parts of non-functional requirement, 1) security
requirements and 2) software quality attributes have been taken
into account. The major considerations under Software Quality
Attributes (SQA) were portability, reliability, availability,
efficiency, safety, flexibility, correctness, testability, accuracy, Fig. 2 Context Level DFD
error tolerance, maintainability, expandability, access control,
In Figs. 2-4, shaded rectangles were used to represent
and installation. Besides, some other non-functional attributes
external entities. External entities in BSK Management
such as the platform, performance, backup, fallback, restart,
Systems can be defined as the departments will be allowed to
and usability were taken into account while specifying the
give access. Processes have been represented by universal
organizational requirements.
process icons. Processes of System Level and Level-1 DFDs
In this study, we have designed 4-modules to perform
are decomposed into a finer level for smooth processing.
company’s four major operations which are Library
Databases have been represented with inventory icons. Data
Management, Account Management, Examination Control, and
flows with an arrow head have been used to show the flow of
Human Resource Management.
the connectors.
We have ensured the technical, economical, and operational
feasibilities of the organization. To ensure technical feasibility,
operational computer configurations and IT skills of the
employee have been inspected. Our investigation found that as
a non-profitable social awareness organization, the software
maintenance cost might be a challenge for the organization to
bear. Therefore, economically feasible software was taken into
consideration. Finally, based on the existing systems and
organizational framework, an operational feasibility has been
ensured and reported to the project supervisor.
Vol:9, No:5, 2015
Fig. 4 (b) Level-1 DFD for Institutional Subsystem

D. Entity Lifecycle Diagram
Fig. 3 System Level DFD
Entity Life-Cycle Diagram is a graphical notation for
Object-Oriented (OO) software development, which purposed
to depict entity states and the possible state changes for entities
of a single type [15]. In addition, Brain [16] argued that there is
no object-oriented software model of life-cycle that has gained
universal acceptance. Therefore, by considering the designing
flexibility and project objectives, we have drawn Entity
Life-Cycle Diagram to represent our software graphically. Fig.
5 shows the Entity Life-Cycle Diagram for BSK Management
System.
E. Data Modeling
In modern days computing, Entity Relationship (ER) model
is considered greatly for designing databases. The conceptual
ER model consists of two major concepts: 1) Entities and 2)
Relationships, which are the associations or interactions
between several entities. Entities can be defined as real-life
objects either animate or inanimate that can be easily
identifiable and distinguishable. The ER diagram shown in Fig.
6 was designed and implemented for BSK Management
Fig. 4 (a) Level-1 DFD for Program Management Subsystem
System. Databases have been developed based on conceptual
entity relationship diagrams and functional relationship. In Fig.
6, rectangles, circles, and diamonds represent entity types,
attributes, and relationship types respectively. In addition, lines
link attributes to entity types and entity types to relationship
types. To describe binary relationships based on cardinality
ratios, One-to-One (1->1), One-to-Many (1->m) and
Many-to-Many (m->m) notations have been used. Logical
relationships have been defined as well during database
implementation.
Vol:9, No:5, 2015
Fig. 5 Entity Lifecycle Diagram
Fig. 6 Conceptual Entity Relationship Diagram
V. SOFTWARE IMPLEMENTATION
This section briefly discusses on the implementation and the
Vol:9, No:5, 2015
operations of the BSK Management System. management, 3) Examination control, and 4) Human resource
management.
A. Interface Design
Library Management Module supported with functionalities
In Human-Computer Interaction (HCI), user interfaces have to perform basic book search operation. Librarians and
traditionally been about designing effective and efficient registered students were targeted users of this module. This
systems. By considering users ability to perform computer module was designed such a way that students can order
operations, we have designed simple and easy-to-operate (purchase) a book online. However, the software does not
interfaces. Proposed software ensures the security and function online payment. Fig. 8 displays a sub-module of
accessibility by password protection. library management module.
B. Technical Specification
We used Microsoft Office Visio 2007 for any sort of
designing including DFD, Rich Picture, and Entity
Relationship Diagram. To prepare Structured English we used
Microsoft Office XP and for presentation, we used Microsoft
PowerPoint.
To develop the final software for the organization, we used

Visual Studio 6.0. We also used JAVA for few activities. We
used Microsoft Access, My SQL, SQL, and Oracle for database
maintenance.
C. Modules & Operations
As stated earlier, organizational behavior and tasks needed to
perform (set by BSK employee) were the key considerations
during software implementation. Due to that fact, the BSK
Management System V 1.0.0 consists of 7-key operational Fig. 8 Library Management Module
buttons under each module. The button 1) ‘Find’ performs the
search operations; 2) ‘Add’ performs basis addition operation Account Management Module processes daily financial
to database; 3) ‘Save’ performs saving data operation that users transactions taken place into the enterprise. Employers under
might need for future references; 4) ‘Delete’ button erases the finance department were given access to the module. This
existing data from the database; 5) ‘Cancel’ performs module assists users to all finance-related works including
cancellation; 6) ‘Print’ button assists users in printing automatic ledge update, create a new transaction, delete
documents if the computer is connected to local or network existing etc. Fig. 9 shows a snapshot of the sub-module of the
printer; and 7) ‘Close’ is used to quit the current module and account management module.
switch to other (if access allowed). In addition, other
operational buttons were created based on modules’ operations.
BSK Management System was developed with password
protection policy. Only authorized users are allowed to access
the system. To access to the modules, users need to insert
accurate user id and password. Fig. 7 displays the login window
that users will experience to access the functionalities.
Fig. 7 Login Window to Access BSK Management System Fig. 9 Account Management Module
In this study, we report four modules that have been Examination Control Module performs tasks related to
developed and delivered to the client. The four modules were students’ education. Teachers can create student profiles and
designed to perform enterprise’s operation under four analyze their performances by using this module. Teachers and
departments, which are: 1) Library management, 2) Account people involved in teaching were main users of this module.
Vol:9, No:5, 2015
Fig. 10 shows working environment with this examination D. Structured English

control module. Structured English QUEry Language (SEQUEL) is
considered as a relational data sublanguage intended for ad hoc
interactive problem solving by non-computer specialists [17].
Keeping end-users into consideration, a version of SEQUEL
has been implemented and documented. Fig. 12 shows the
SEQUEL for BSK Management System.
Fig. 10 Examination Control Module
Human Resource Module was developed to help employers

under HR department to perform their tasks related to human
affairs. Access to this module were set to HR staffs and people
working in the top management of the organization. A snapshot
of human resource module has been shown in Fig. 11.
Fig. 12 SEQUEL of BSK Management System

E. Rich Picture
The Rich Pictures are generally constructed by interviewing
people [18]. Rich pictures originated in the Soft System
Methodology (SSM) [19]: Soft systems methodology (SSM) is
an approach for tackling problematical, messy situations of all
kinds. It is an action-oriented process of inquiry into
problematic situations in which users learn their way from
finding out about the situation, to taking action to improve it
[20].
The importance of drawing a rich picture scenario was
because of the assumption that, the newly developed system
will affect the way people work. Fig. 13 shows the Rich Picture
of BSK Management System.
As a non-profitable organization, donors are the key source
of financial support in BSK. Therefore, we have designed rich
picture from a donor. It can be mentioned that drawing rich
Fig. 11 Human Resource Module pictures are the matter of debate. Depending on the type
organization and type of activities, the rich picture might vary.
An access to these modules was set based on client’s
In this study, we have tried to reflect the operation of the
demand. Another access was granted to the person who will be
enterprise by drawing the rich picture (shown in Fig. 13).
responsible to change privacy policies.
Vol:9, No:5, 2015
Fig. 13 Rich Picture of the Enterprise
F. Data Dictionary
Databases have been managed with active data dictionary. In I. Delivery and Maintenance
Data Management System (DMS), Data Dictionary is an The software was delivered to the client within the given
approach to represent a set of information describing the timeframe. Software installation and proper guidance to access
contents, format(s) and structure(s) of databases and the the system have been provided in engineering manner.
relationship between its elements. Werts [21] described
step-by-step instructions and demonstrated how to customize VI. USABILITY TEST
planning so the installed dictionary meets an organization's We have conducted a survey to investigate the usability of
specific needs. The article also reviewed basic data concepts our proposed system. We have also interviewed the company
and data-related problems, discussed diverse approaches to employees along with an assessment survey to ensure the
these problems, and described ideas and features of data accuracies and performances of the installed new software.
dictionaries.
A. Participant Details:
G. Testing 10 employees and 10 students participated in the survey. The
Our proposed software BSK Management System has been participated students were involved in voluntary social works
tested in engineering manner. During software testing, bugs and also involved in BSK’s daily operations.
have been removed and compatibilities have been ensured.
B. Materials & Method:
H. Documentation Aid Participants were, at first, asked to perform some basis
After found out all required information for our software we transactions on the newly installed software. Then, participants
have recorded all the requirements accurately and made a were asked to evaluate our software under 8 perspectives
reliable and complete documentation for the further (shown in Fig. 14) based on their experiences. Each participant
improvements. was asked to use our system for 30 minutes. The system’s
Vol:9, No:5, 2015
operation and functionalities have been explained in advance. approach will assist software engineering students and IT
After the 30-minutes session, we asked them to feedback analysts to understand the phases involved in the Waterfall
their impression on the usability of the software. An assessment model effectively.
questionnaire with 8 different perspectives of software was At first, we introduced mid-sized enterprise software named
provided to them. We also interviewed the participants about “BSK Management System”, which assists enterprise software
the software afterwards. clients with information resource management and perform
complex organizational tasks. The proposed system assists
enterprise software clients to assist with information resource
management under limited financial budget. The system was
designed and developed on a non-profitable organization
located in Bangladesh to perform its daily operations. The
organization is involved in activities like to promote reading
habits, enlightenment, and progressive ideas among students
and the general public in Bangladesh. The system analysis and
design phases have been done based on the given information
on the organization.
In the system analysis phase, generic 7-phases (Preliminary
Investigation, System Analysis, System Design, Coding,
Testing, Conversion, and Maintenance) of the Waterfall model
had been investigated properly in engineering manner. The
reasons for using the Waterfall model were 1) it allowed
Fig. 14 Questionnaire Used in Usability Test designing flexibility, 2) rigidity, 3) phases do not overlap with
C. Result each other, 4) software testing in every stage, 5) easy
debugging, 6) less ambiguity in requirement gathering phase,
The survey result revealed that, all of the participants
7) limited budget, 8) strict timeline, and 9) quick
evaluated our system positively. The result indicated that,
implementation.
approximately 60% evaluation (8 perspectives & 20
At the beginning of this study, we have gathered all the
participants) was found ‘Excellent’. Approximately 30%
requirements to proceed to system analysis phase. We have
feedback was noted as ‘Very Good’ and approximately 10%
interviewed the employees of the enterprise and analyzed the
noted as ‘Satisfactory’. None of the participants assessed our
infrastructure of the enterprise as the part of requirement
system as ‘Difficult to Operate’ and ‘Very Difficult to Operate’.
collection. Secondly, based on the gathered information, we
Therefore, we can conclude that our system features simple
have drawn the DFDs in context level, system level, and level 1
interfaces, easy operation and maintenance, quick processing,
of the enterprise. Thirdly, we have drawn the entity lifecycle
reliable and accurate operations. After interviewing the users of
diagram for the flexibility of the project. Fourthly, conceptual
this software, we knew that they took the solution very frankly
entity relationship diagram has been designed. Later on,
and they were satisfied with the software. Therefore, we can
databases have been implemented base on conceptual and
conclude that the employee will get everything they require by
logical relationships between entities. Fifthly, we have
using this software.
developed and reported 4-major modules for the enterprise.
Four modules for library, accounts, examination and HR have
VII. DISCUSSION
been developed and delivered to the client. We have designed
ICT is a potentially powerful tool for extending business. simple interfaces because of users’ inadequate knowledge on
Not only big-size enterprises are investing in ICT-based technologies. Developed software has been tested and
information management, but also many mid-size and debugged with proper engineering ways.
small-size enterprises moving forward to it. The massive flow Then, we have supported this study with SEQUEL, rich
of ICT in organizations has been noticed significantly in picture of the enterprise, and built a data dictionary. A
third-world countries in recent decades. Enterprises are ready to documentation of the entire system has been prepared for
adopt ICTs because it features transcend time and space. further improvements.
However, limited financial budgets lack of IT skills, and lack of Finally, the software has been delivered to the client within
enough infrastructures enterprises are stepping back. To design the given time frame. The software had been implemented and
information resource management software for small and users of the system have been trained to use the system.
mid-size enterprises under budget cost and strict deadline was Moreover, we have conducted a questionnaire survey with
always problematic for engineers. At the same time, inadequate 20 participants to investigate the usability of the system. The
knowledge of different approaches to software engineering is a result revealed that users found our system easy to operate,
major challenge while working under the limited budget and a accurate transactions, fast processing and easy to navigate. An
strict deadline. interview followed by the questionnaire survey has been done.
Therefore, in this study, we have reported an approach to The interview indicated that users of the system are quite happy
design enterprise software under a strict deadline. Our proposed to use the system. Most of the participants agreed that the
Vol:9, No:5, 2015
proposed system would help them to fulfill their daily [2] K. S. Nantz. “Supporting End-User Application Development with the
Information Transformation-Analysis-Management Model”, In
transaction. Managing Information Resources in the 1990s: Proceedings of 1990
Time to complete the entire project set by the enterprise was Information Resources Management Association International
20-weeks. Table I displays the allocation of time planned and Conference (p. 66). IGI Global, 1990.
required to complete each phase. [3] J. L. Whitten, V. M. Barlow, and L. Bentley, “Systems analysis and
design methods”, McGraw-Hill Professional, 1997.
[4] P. Palvia, J. T. Nosek, P. Palvia, and J. T. Nosek, “An empirical
TABLE I evaluation of system development methodologies”, In Managing
PROJECT TIMELINE
information resources in the 1990s: proceedings of 1990 Information
Planned Time Required Time Resources Management Association international conference (p. 72),
Phases
(Days) (Days) 1990.
Preliminary Investigation 12 11 [5] N. B. Ruparelia, “Software development lifecycle models”, ACM
Requirement Analysis 22 22 SIGSOFT Software Engineering Notes, 35(3), 8-13, 2010.
Data Flow Diagram 28 24 [6] H. D. Benington, “Production of large computer programs”, In
ICSE (Vol. 87, pp. 299-310), 1987.
Entity Relationship Diagram 14 12 [7] W. W. Royce, “Managing the development of large software systems”, In
Backend 7 7 proceedings of IEEE WESCON (Vol. 26, No. 8), 1970.
User Interface 14 10 [8] S. Conger, “Software development life cycles and methodologies: Fixing
the old and adopting the new”, 2010.
Testing 7 3
[9] S. Balaji, and M. S. Murugaiyan. "Waterfall vs v-model vs Agile: A
Handover & Implementation 7 5
Comparative Study on SDLC" JITBM & ARF 2.1: 26-30, 2012
Usability Test 7 5 [10] C. Sue. "Software development life cycles and methodologies: Fixing the
Others 7 6 old and adopting the new." (2010)
[11] R. Heeks "Information systems and developing countries: Failure,
success, and local improvisations." The information society 18.2:
A complete understanding of the approach followed to 101-112, 2002.
develop enterprise software in this article will give engineers [12] K. R. Linberg, "Software developer perceptions about software project
ideas to plan, schedule, and deliver a project successfully under failure: a case study", Journal of Systems and Software 49, no. 2: 177-192,
strict deadline and a budget cost. 1999.
[13] P. P. Chen, “A Preliminary Framework for Entity-Relationship Models”,
In ER (pp. 19-28), 1981.
VIII. FUTURE WORKS [14] Y. L Chen, "Data Flow Diagram." Modeling and Analysis of Enterprise
and Information Systems. Springer Berlin Heidelberg, 85-97, 2009.
Software development by using SDLC’s other models- in a [15] https://support.ca.com/cadocs/0/CA%20Gen%208%205-JPN/Bookshelf
similar environment would be a recommended future work for _Files/HTML/AnalysisGuide/index.htm?toc.htm?1100359.html
new software engineers and analysts. As design-acuity gap [16] H. S. Brian, and J. M. Edwards. "The object-oriented systems life cycle."
Communications of the ACM 33.9: 142-159, 1990.
remains a challenge for software failures, further investigation [17] M. M. Astrahan, and D. D. Chamberlin. "Implementation of a structured
needs to be taken to the improve design-acuity gap. A English query language." Communications of the ACM 18.10: 580-588,
large-scale project by using this approach needs to be 1975.
[18] A. Monk, and S. Howard. "Methods & tools: the rich picture: a tool for
conducted. reasoning about work context." interactions5.2: 21-30, 1998.
Currently, BSK Management System v1.0.0 supports four [19] P. B. Checkland, "Soft systems methodology." Human systems
major modules. Developing five more modules are under management 8.4: 273-289, 1989
[20] P. B. Checkland, "Soft systems methodology." Encyclopedia of
consideration and will certainly be taken into action as future Operations Research and Management Science. Springer US, 1430-1436,
works. 2013.
[21] C. J. Wertz, “Data Dictionary: Concepts and Uses”, John Wiley & Sons,
Inc., 1986.
ACKNOWLEDGMENT
We, hereby acknowledge Mr. Shamimul Hasan Azim
(Researcher, VirginiaTech USA; ex-Faculty, Stamford
University Bangladesh) and Assistant Professor Kamruddin
Md. Nur (PhD Candidate, Pompeu Fabra University SPAIN;
Faculty, Stamford University Bangladesh) for their constant
advice and guidance throughout the project. In addition, we
show our deepest appreciation to the honorable Chairman, BSK
to grant us permission to conduct research activities and publish
the outcome.
We would also like to express our special thanks to the
participants of the experiments. Without their help and support,
this study would not have completed successfully.
Authors would like to dedicate this project to the victims of
Cyclone Sidr in 2007, Bangladesh.
REFERENCES
[1] C. R. Necco, C. L. Gordon, and N. W. Tsai, “Systems analysis and design:
current practices”, MIS Quarterly, 461-476, 1987

3 (2) 131-141

Uploaded by

Copyright:

Available Formats

3 (2) 131-141

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3 (2) 131-141

Uploaded by

Copyright:

Available Formats

See discussions, stats, and author profiles for this publication at: https://www.researchgate.

A Cost Effective Approach to Develop Mid-size Enterprise Software Adopted

Article · September 2018

Mohammad Nehal Hasnine

The user has requested enhancement of the downloaded file.

A Cost Effective Approach to Develop Mid-size

dissemination, and acquisition of data. Due to these facts,

T HE processes to develop computer-based information

development effort. However, to our best understanding, not significant amount

(how), detailed to design (how), coding and unit testing A. In-a-Nutshell

C. System Analysis & Design

Fig. 1 Waterfall model with iterative feedback

Fig. 4 (b) Level-1 DFD for Institutional Subsystem

Fig. 5 Entity Lifecycle Diagram

Fig. 6 Conceptual Entity Relationship Diagram

To develop the final software for the organization, we used

Fig. 10 shows working environment with this examination D. Structured English

Fig. 10 Examination Control Module

Human Resource Module was developed to help employers

Fig. 12 SEQUEL of BSK Management System

Fig. 13 Rich Picture of the Enterprise

You might also like