1

2
3
4
1.1. Introduction to CBA

CBA which is an association for college basketball needs an information system to record and
manage different communities of basketball and their respective activities. Here in this
association, every team represents one university where there can be multiple teams from a
single university. Every team can have multiple coaching staff but a coach can’t facilitate
multiple teams.

Association’s proposed new system is to keep records of every game that is being played in the
universities on yearly basis. There is the participation of numbers of teams in a tournament and
there are numbers of the tournament organized by different universities, where every team
representing a particular university can participate. Therefore, all the final results of those games
(Win, Draw, or loss) will get stored in the system.
Here players can play many games as of their performance whereas they will also get seated on
the bench in case of injuries, average performance, or any other reasons. The new system is also
to keep the personal record of every individual player, where it will record the points scored by
the players, committed fouls, assist made, on-ground duration, and many more.

5
1.1.1. Current Business process
Every year the association organizes a camp where the young players serve in a youth basketball
camp as a counsellor. They must supervise players at camp and interrelate with the camper’s
daily activities. Any CBA members or college students, who are enrolled with the association
can join the camp. The camps will be held at the different locations of the city where each camp
will have several players serving as counsellors and those counsellors are free to serve at
different camps as of requirement. Currently, all these data of players, camps, counsellors are
stored in file through a file-based approach, which is creating difficulties for association in data
management and report generation. To cope with this problem the association has come up with
the idea of the new digital and database-based system.

1.1.2. Business rules for the proposed system

i. There should be a mandatory function for CBA staff to set down and manage information
regarding games played, players’ and team’s achievements, camps conducted, and all.
ii. Members of the association should be enabled to open a new account as a player,
counsellor coach, or general public who can later view games schedules, register in
tournaments or games, and get details about the camps to be conducted.
iii. Once members open an account, they should be notified of new events, camps, games or
may often get personal suggestions from the association.
iv. The new system should be able to generate performance reports of teams, players, and
coaches, as required on a weekly, monthly, or yearly basis.
v. New system should be able to categorize players, coaches, and teams based on criteria
like location, age, and gender of the individual.
vi. The data should be collected such that the system should be able to compare the
performance of different players, which helps in selecting players and hiring them for
important jobs.
vii. The coaches should be able to track the data on the field like the crossovers, specific
moves made, defend and assist of the players, which will help them to prepare their
gameplan, player’s position, and all.

6
1.2. Problem statements
1.2.1. Information management
To date, the association is working with the traditional file-based approach of data management
which creates difficulty in recording and managing personal data of players, coaches,
tournaments, and all.

1.2.2. Lack of communication

Since the association is not working with the digital platform, it gets hard for them to record
personal information of members, team registration, publishing game schedule, and notice.

1.2.3. Generating report

Association needs to generate reports regarding tournaments, camps, and games for information
purposes, but generating report manually takes more time than it would have taken to generate
reports digitally. Also due to lack of proper data management, generating weekly reports gets
even much harder.

1.2.4. Demographic criteria

The current system found it difficult to track and manage data of players, coaches, and members
based on gender, age, location, and their respective colleges.

1.2.5. Lack of on-field data

The current system couldn’t properly record and manage the on-field record of the players i.e.,
tracking individual performance. There is a very high chance of data redundancy and data being
misplaced.

7
1.3. Scopes and objectives of the proposed system
1.3.1. Proper data management
The new system is proposed to ease the data recording and managing task, storing all the data of
players, teams, coaches into the personal database of the association. Now, staff can extract and
provide the exact data from the database in need.

1.3.2. Information flow

The association has proposed to upgrade itself into a digital system, where it will be providing
events information and games schedules to its members digitally.

1.3.3. Report generation

Based on data stored on the database, the system could easily generate a required report on a
weekly, monthly, and yearly basis without any redundancy issues.

1.3.4. Proper data classification

The database of the system will record the information of players, members, and coaches based
on demographic criteria, which will help to extract the required data of an individual in no time.

1.3.5. On-field data of the players

With the help of the On-field data stored on the system’s database, couches could easily track
their previous performance records, opponent’s records, and their player’s performance history
against a particular team and in a particular tournament. This will help them to prepare
accordingly and build a game plan.

8
1.4. Project Scheduling
1.4.1. Gantt chart: This chart represents the timeframe for different sub-tasks performed from
the start of a project to its completion.

Figure 1: Gantt Chart

1.4.2. Pert Chart: This chart represents the scheduling and mapping of different sub-tasks
performed during the project development.
Figure 2:Pert Chart

Figure 3: Critical Path Calculation

2. Agile Principles and IS methodology

2.1. Agile Principles
2.1.1. Communication on daily basis between developers and business people.
When a business client or any organization asks a software company to build business software.
They come up with initial requirements regarding their business process. The developers analyse
the requirement and start working on that project. During the system development process, the
developers need to be in touch with the business authorities, who have assigned the project. This
will help developers to get updated on the requirement of the system, current market
requirements, and business processes. Whereas the developers can also communicate easily with

9
the client on required changes in the system, additional time is needed to complete the project,
and the budget aspects as well. As a software development consultant, I will make sure to make
communication easier between CBA authorities and the developers. Information, system
progress, revised requirement, time, and budget will be easily circulated among the clients and
developers. This will help in the smooth development process of the system and will reduce the
chance of miscommunication between the two parties (Martin, Rabaey, Chandrakasan, &
NIkolic, 2003).

Right from the beginning, the project should be in the hand of trusted employees. Only good
human resources can lead a project to completion in time with an allocated budget and all the
business requirements. From the planning to deployment stage of the system, only skilled,
passionate, and motivated individuals should be assigned. As a software development consultant,
I will make sure to assign this project of CBA to a well-organized and motivated system
development team, who will not only work for fulfilling the basic requirement of the system but
also work on the non-functional and additional features of the system. Also, I will take the
responsibility to cover up this project of CBA with experienced developers and mentors who
could give valuable suggestions and contribute to the development of a feasible system.

10
2.1.2. Self-organizing teams produce the best architectures, needs, and designs.
(NP000528)
In every sector, while working on the new plan, we need to gather and analyze different data of
different types to make the best outcome of working (Goyal, 2020). Likewise, in a software
development company, there are many aspects and combinations of work to be analyzed,
considered, and reviewed before starting a new project. While in the planning phase, R&D teams
plan different ideas, approaches, and paths to complete a task. They make lists or purposes for
other architectures, requirements, and designs to achieve or develop a system. They choose them
based on availability, customer requirement, easier to maintain, easier to use, protection of the
system, protection of data, etc. They also generate and perform different types of testing to find
the best among them and choose them to develop a new system (Amerongen, 2009).

They enabled professionals to concentrate their efforts on their area of expertise and provide the
finest answer feasible. A user interface was created by the interaction designer. The architect
established a global systems model, developers wrote code, and infrastructure specialists built
the environment in which the program would execute (Amerongen, 2009). Everyone was highly
specialized and provided the finest answer possible within their ability. However, when all of
these parts were combined, nothing worked. It is a myth that professionals can plan and predict
everything ahead of time. Agile's core concept is that motivated, independent, and talented teams
will produce the greatest results and products.

11
2.1.3. The team considers how to improve its effectiveness regularly and makes
adjustments as needed. (NP000528)
The project team’s priority should be to advance their abilities and procedures to develop and
improve (Rajkhowa, 2020). On a daily basis, self-organizing teams should monitor their work
performance and should improve their methods or behavior toward work to achieve and improve
overall work. None of the individuals is perfect, and none of the teams can be run perfectly.
Therefore, an experienced agile team can find the short comes of the project and take actions to
improve on those areas. (Parkhurst, 2015).
It is critical to do regular reflections or retrospectives because teams often become caught in the
cycle of moving from one problem to the next while attempting to reach the next goal.
To genuinely improve, the team must reflect on what occurred and consider what may be done
differently the next time (Parkhurst, 2015).

12
2.1.4. Customer satisfaction through timely and consistent supply of valuable software.
(NP000534)
The opinions of project participants are different. From a developer's point of view, valuable
software is beautifully designed using all object-oriented principles of encapsulation, inheritance,
and abstraction. From the end user’s point of view, valuable software has a rich and customized
user interface and numerous features that facilitate day-to-day operations. Support departments
believe that valuable software is easy to install, configure, manage, and inexpensive to maintain.
Entrepreneurs only want effective TCO value related to company value. To get a solution to this
query you need to get returned to the commercial enterprise in case of an undertaking. The
commercial enterprise case units the GOALS of the undertaking in opposition to the charges of
making the deliverable to attain the goal. The Software is simply one (in lots of instances the
maximum important) of the deliverables of the undertaking and the purchaser makes use of the
deliverable to attain the goal.
The User interface in an enterprise-to-enterprise environment (or inner application) in which the
proposed software program an unmarried device for information retrieval their number one aim
is to automate the procedure and decrease the prices for maintenance. The consumer interface
must be practical and branding may be constrained to an unmarried logo. The user interface
layout is derived from the libraries or gear available.
 Role of the undertaking supervisor in developing treasured software
It is the function of the undertaking supervisor (and the entire team) to cognizance the eye on
one’s functions that truly remember and make a distinction for this client. Try to shop the
dialogue the nitty-gritty info to the factor that the client has running and treasured software.

13
2.1.5. Consistent focus on technical excellence and outstanding design. (NP000534)

The first time I checked out this precept I thought: “How is this possible.” Agility makes a
specialty of quick turning in an operating software program I skilled this is not always true.
Attention to technical excellence is making the agile system operate better. Technical excellence
could make the improvement system greater flexible. In this context, I would like to factor out
that there is a distinction between technical excellence / true layout as compared to complicated
layout and technical complexity.
 Smart era and clever layout
Every developer, architect, and clothier must paint with concepts of the clever layout of their
minds. There are simplest concepts: 1) the idea has two paintings and 2) different group
individuals recognize and are cap in a position following the principle. Smart era and proper
layout have their best benefit while its miles are used for the advantage of the entire software and
the entire group. Not only for sub-most desirable enhancements for an unmarried feature or an
unmarried developer. A good terrific era and proper layout must make coding clean and the
software modular, extra bendy, and adaptable. By the usage of the proper frameworks and
assisting equipment you can supply better first-class software programs tons quicker than you
wherein used to. In exercise this indicates the usage of frameworks for not unusual place duties
like authorization, patience, and navigation and equipment for building, freeing, and deploying
your software.
 Monitoring and assessment
Within your crew, you need to reveal the precise utility of layout and generation. Your venture
must have numerous evaluation moments in which the utility of layout styles and generation are
reviewed. The deviations from the layout should be corrected or (whilst approved) supplied with
more documentation. Besides reviewing the precise utility of requirements in layout and
generation you have gotten if you want to evaluate the correctness of the selected generation.

14
2.2. IS methodologies
2.2.1. SCRUM Methodology
Scrum is one of the methodologies of IS development which is an iterative and incremental-
based process. This agile framework is flexible, adaptive and is designed to come out with a
user’s-based system. This methodology enables customers and stakeholders to come up with
their requirements for a business system and prepare a system requirement document as their
preferred requirement. This methodology begins with collecting business requirements of the
system from users and stakeholders and then prioritizing the fundamental requirement as the
product owner wants to acquire (Rubin, 2012).
Key concepts of Scrum Methodology:
(i) User Stories

At the first step, the system users, developer, stakeholder, and company executive come up with
general ideas of system requirements. They set their requirement as their needs and
understanding. This is an important stage since the product owner can get the perspective of the
customer and what would they like to prefer in the system or business process.
(ii) Product Owner

Once the requirement from all the users, developers, and stakeholders are analyzed, the product
owner verifies, whether all the system requirements are mentioned or not, whether there are
some missing or unwanted requirements. Therefore, reviewing the requirement the product
owner comes up with the final requirement for the system, preferring the customers, developer’s
requirement, and some additional requirements (if needed) as well.
(iii) Development Teams

After finalizing the requirements, the product owner assigns a system development team to turn
these system requirements into their system or business process. A development team that
contains individuals of different skills like programming, database management, User interface,
research analyst, and leadership come up together to make a well-functioning term which can
work together, implementing their respective skills to make a functional system as of the product
owner’s requirement.

15
(iv) Scrum Master

The scrum master is one, who is the leader of the system development group and takes the
responsibility to handle overall problems and gaps that occurred during the developmental
process using agile methodology. Scrum Master is also responsible for giving ideas and solving
the problem that occurred during the developmental phase (Watts, 2021).
(v) Sprint

Sprint in scrum is a cycle of tasks, in which the assigned task is to be completed in a certain time
frame. In this process, the whole developmental process is split into different sub-tasks and the
development team takes the challenge to complete these sub-tasks in a certain period.
(vi) Backlogs

Backlogs in scrum methodology is a list of fundamental requirements or sub-tasks that need to

be completed to complete the system development project, delivering a functional and business-
oriented system.

 Features of Scrum

i. The overall required features for the system are collected through users and stakeholders
which are later again analyzed by the product owner. Therefore, there is very little chance to
miss user-based requirements in the system.
ii. Since the development team is composed of different individuals with different project-
related skills, there is a high expectation for a functional system to come out as a result.
iii. The leader of the project, helps the team, addressing resources problem and making the team
updated with the altered requirement of clients.
iv. The concept of the sprint in this project is highly effective for the progress of the system
since multiple small project-related tasks are initiated to complete in a certain timeframe.
This will also help the team to build the system in the allocated timeframe.
v. The concept of backlogs in scrum helps to figure out the fundamental requirement of the
system so that critical tasks will be completed within the timeframe as per the system
requirement.

16
 Advantages of Scrum

i. This methodology is cost-effective where every further step taken during system
development is organized and goes smoothly, fulfilling the system requirement.
ii. Since users and stakeholders can ask for their requirements from the system and the system
requirement can alter as of user’s requirement, this framework is adaptive and flexible at the
same time.
iii. This framework motivates the system development team to work, allowing the individual
with different skills to come up together and work as a unit. Here scrum master plays a vital
role in maintaining a healthy working environment in the project, where every individual is
motived and driven to come up with the required business system.
iv. With the help of sprint, different sub-task of the project can be accomplished in the allocated
time frame, hence the overall time taken to complete the project can be predicted easily.
v. Ensures continuous feedback.
vi. With the completion of every sub-task, the report of project progress is reviewed by the
scrum master and is sent to the product owner, if the product owner wants some chance in the
work done, he/she will ask for additional or removal of certain business functionality in the
system.

17
 Disadvantages of scrum

i. Scrum methodology more focuses on the sprint, where multiple sub-tasks are challenged
to complete in a certain time, but the overall timeframe required for the project is missed
out along the process.
ii. This methodology requires teamwork, where every individual of the team with different
skills needs to come up together for the project completion, in case any individual fails to
put on his skills to the project, the overall team needs to bear the result, which may even
lead to project failure.
iii. This project needs experienced working individuals in the project, who has earlier
worked with a system development team. Only these kinds of individuals can assure
project success.
iv. This methodology is hard to implement in complex and large projects because the total
time frame for the project is not determined and the changing requirements from the
clients make it difficult for the team to complete the large project in a certain timeframe.
v. Because of the changing requirements for the system and the activity of sprint, the team
member needs to conduct a meeting regularly, which could be time-consuming and
frustrating for the team members.
vi. Because of changing system requirements and multiple sub-tasks, the overall functional
quality of the system is hard to maintain unit the project team follows a strict testing
process.

18
2.2.2. Web IS Development Methodology

The multi-view framework for information systems development is the earliest web-based
system development method introduced by Vidgen (Shaffi, 2013). Multi-view is also known as
the base or building block of web-based system development methodologies and was designed to
give an alternative form to the trend that system development focuses on engineering methods
and rules.

WISDM "provides a framework for combining ordinary structure development strategies with
web-based strategies to furnish a complete framework that spans e-business approach evaluation
to software program deployment” (Taylor, 2006). The adaption of the ISD methods matrix is an
instance of this. A modern approach to overall improvement focuses on the more general aspects
of web-based data systems. It combines website development approaches with traditional IS
development skills in database and software design (Shaffi, 2013). Here are described the
different areas, where WISDM mainly focuses on.

i. Organizational Analysis: Organizational analysis is a multi-view soft systems technique

that focuses on situations with a high level of complexity and many stakeholder interests.
(Taylor, 2006).
ii. Information analysis: The user needs, in this case, has the goals of new system information
for the development of the system. For example, the condition might be of paper graphical
notations or a prototype of the software. This model is supposed to represent the functionality
of the new system’s proposal. (Shaffi, 2013).

iii. Work Design: It aims to build a relationship between the customer and the employee
(Shaffi, 2013). First, there is management in the organization. The administration establishes
the employment criteria. To satisfy an employee, these needs must match the employee's
work expectations and job requirements

19
iv. Human-computer interaction: It represents the interaction of users with the system
interface, as well as the relationship between technology and work design (Taylor, 2006).
The customer's technical expertise, experience, and expectations should all be considered
while designing the user interface. The main focus of web developers should be on the
interface design, which should be user-friendly, accessible, secure, and ergonomically
supporting.

v. Technical Design: The website's development is aided by technical design. This design
describes the website's programming architecture and data structure (Shaffi, 2013). Standard
HTML pages comprise HTML code, which specifies the Web page's structure and content.
Customers, project managers, website developers, and stakeholders all have a role in
influencing each other's goals, policies, and actions, all of which impact the website's future
results.

 Advantages of WISDM
i. It combines website development approaches with traditional IS development skills in
database and software design.
ii. During the project development, each method is equally prioritized.
iii. The adaption of the ISD methods matrix is an instance of WISDM.

 Disadvantages of WISDM
i. The fundamental flaw in this method is that it makes no specific advice for identifying and
analyzing stakeholders and their perspectives.
ii. This method uses five approaches that make this long.
iii. WISDM is not so popular due to the lack of documentation and resources available.

20
2.2.3. V-Model
The V-model is a subtype of the SDLC (Systems Development Life Cycle) model in which the
activities are performed in such a V-shape in sequence. Systems for testing and evaluation are
sometimes referred to as verification and validation models. Each stage of development is
heavily linked to the testing process, depending on the test stage and the connection of each
development process. After the previous phase has been completed, the subsequent step will
commence. That is to state, there is a test action for each construction process. Developing User
Acceptance Testing Designing System Tests Implementing Integration Tests Test just at cell
level design (Russo, Fitzgerald, & Stolterman, 2002).

Figure 4: V-Model

21
 Features of V-model

i. Large to small: Testing in the V-Model is done hierarchically. The project's high-level
design and detailed design phases, for example, are based on the requirements provided by
the project team. The requirements defined by each of these stages get more specific and
detailed as they progress.
ii. Scalability: This notion implies that the V-Model concept can be used in any IT
(Information Technology) project of any size, complexity, or duration.
iii. Data/Process Integrity: The concept is that successful project development necessitates data
and process integration and consistency. A processing element must be identified for each
need.
iv. Tangible documentation: Once the system is developed, system documentation will also get
prepared for future reference and to be reviewed by clients or the development team.
v. Cross-Referencing: Cross-referencing is a term that refers to a direct link between a need
and a checking-out interest.

 Advantages
V-model is quite easy to understand because the testing practices such as planning and test
development commence long before coding. This is a very trained model and steps are
completed one at a time. It is suitable for small plans with easy-to-understand requirements. This
saves a lot of time. Hence a better risk of fulfillment over the waterfall model.

 Disadvantages
It is a Very inflexible methodology because the period and the requirement cannot be adjusted
over the project. It is hard to implement for a complex project. The prototype for the system
cannot be determined before the system is developed.

22