De Guzman, Marion Macarius M.

BSA-2B

1. What is SAD?

Systems Analysis and Design (SAD) is a broad term for describing methodologies for
developing high quality Information System which combines Information Technology, people and Data
to support business requirement. A SAD methodology can also be referred to as a Systems Development
Life Cycle (SDLC) that includes the development process as well as the ongoing maintenance process.
The classic SAD methodology is the waterfall model which was originally conceived for the software
development; hence the focus is on programming. The key phases of the waterfall model are the analysis
and design phases. It is obvious that there will always be an implementation phase and an operations
phase. The analysis phase focuses on understanding the needs of the organization. The design phase
focuses on designing the physical aspects of a system to support the needs of the organization.
Understanding SAD is the first step in developing a successful project. However, the proper application
of SAD principles is the key to making a project successful. In order to properly apply these principles,
an analyst must be able to lead, communicate and sell the SAD principles to the project team.

2. Techniques in SAD

The Software Development Life Cycle (SDLC) is the software development world’s spellcheck
— it can flag errors in software creation before they’re discovered (at a much higher cost) in successive
stages. But it’s much more than that, of course: SDLC can also lay out a plan for getting everything right
the first time. The SDLC process involves several distinct stages, including planning, analysis, design,
building, testing, deployment and maintenance. What's the best SDLC methodology? Each of the
approaches varies in some ways from the others, but all have a common purpose: to help teams deliver
high-quality software as quickly and cost-effectively as possible. Here are six methodologies, or models,
to consider.

A. Agile
The Agile model has been around for about a decade. But lately, it has become a major driving force
behind software development in many organizations. Some businesses value the Agile methodology so
much that they are now applying it to other types of projects, including non-tech initiatives.
In the Agile model, “fast failure” is a good thing. The approach produces ongoing release cycles, each
featuring small, incremental changes from the previous release. At each iteration, the product is tested.
The Agile model helps teams identify and address small issues on projects before they evolve into more
significant problems, and engage business stakeholders and get their feedback throughout the
development process.
As part of their embrace of this methodology, many teams are also applying an Agile framework known
as Scrum to help structure more complex development projects. Scrum teams work in “sprints,” which
usually last two to four weeks, to complete assigned tasks. Daily Scrum meetings help the whole team
monitor progress throughout the project. And the ScrumMaster is tasked with keeping the team focused
on its goal.
B. Lean
The Lean model for software development is inspired by lean manufacturing practices and principles.
The seven Lean principles (in this order) are: eliminate waste, amplify learning, decide as late possible,
deliver as fast as possible, empower the team, build integrity in, and see the whole.
The Lean process is about working only on what must be worked on at the time, so there’s no room for
multitasking. Project teams are also focused on finding opportunities to cut waste at every turn
throughout the SDLC process, from dropping unnecessary meetings to reducing documentation.
The Agile model is actually a Lean method for the SDLC, but with some notable differences. One is
how each prioritizes customer satisfaction: Agile makes it the top priority from the outset, creating a
flexible process where project teams can respond quickly to stakeholder feedback throughout the SDLC.
Lean, meanwhile, emphasizes the elimination of waste as a way to create more overall value for
customers — which, in turn, helps to enhance satisfaction.

C. Waterfall
Some experts argue that the Waterfall model was never meant to be a process model for real projects
regardless, the Waterfall model is widely considered the oldest of the structured SDLC methodologies.
It’s also a very straightforward approach: finish one phase, and then move on to the next. No going
back. Each stage relies on information from the previous stage and has its own project plan.
The downside of Waterfall is its rigidity. Sure, it’s easy to understand and simple to manage. But early
delays can throw off the entire project timeline. With little room for revisions once a stage is completed,
problems can’t be fixed until you get to the maintenance stage. This model doesn’t work well if
flexibility is needed or if the project is long term and ongoing.
Even more rigid is the related Verification and Validation model — or V-shaped model. This linear
development methodology sprang from the Waterfall approach. It’s characterized by a corresponding
testing phase for each development stage. Like Waterfall, each stage begins only after the previous one
has ended. This SDLC model can be useful, provided your project has no unknown requirements.

4. Iterative
The Iterative model is repetition incarnate. Instead of starting with fully known requirements, project
teams implement a set of software requirements, then test, evaluate and pinpoint further requirements. A
new version of the software is produced with each phase, or iteration. Rinse and repeat until the
complete system is ready.
Advantages of the Iterative model over other common SDLC methodologies is that it produces a
working version of the project early in the process, and makes it less expensive to implement changes.
One disadvantage: Repetitive processes can consume resources quickly.

5. Spiral
One of the most flexible SDLC methodologies, the Spiral model takes a cue from the Iterative model
and its repetition; the project passes through four phases (planning, risk analysis, engineering and
evaluation) over and over in a “spiral” until completed, allowing for multiple rounds of refinement.
The Spiral model is typically used for large projects. It enables development teams to build a highly
customized product, and incorporate user feedback early on in the project. Another benefit of this SDLC
model is risk management. Each iteration starts by looking ahead to potential risks, and figuring out how
best to avoid or mitigate them.

6. DevOps
The DevOps methodology is the newcomer to the SDLC scene. It emerged from two trends: the
application of Agile and Lean practices to operations work, and the general shift in business toward
seeing the value of collaboration between development and operations staff at all stages of the SDLC
process.
In a DevOps model, Developers and Operations teams work together closely — and sometimes as one
team — to accelerate innovation and the deployment of higher-quality and more reliable software
products and functionalities. Updates to products are small but frequent. Discipline, continuous feedback
and process improvement, and automation of manual development processes are all hallmarks of the
DevOps model.

3. WHAT IS VBA?
VBA (Visual Basic for Applications) is the programming language of Excel and other Office
programs. VBA stands for Visual Basic for Applications. Excel VBA is Microsoft's programming
language for Excel. Excel analysis is ubiquitous around the world and used by businesses of all sizes to
perform financial analysis. and all the other Microsoft Office programs, like Word and PowerPoint.
Visual Basic for Applications (VBA) is part of Microsoft Corporation's (NASDAQ: MSFT) legacy
software, Visual Basic, which the company built to help write programs for the Windows operating
system. Visual Basic for Applications runs as an internal programming language in Microsoft Office
(MS Office, Office) applications such as Access, Excel, PowerPoint, Publisher, Word, and Visio. VBA
is an event-driven tool, which means that you can use it to tell the computer to initiate an action or string
of actions. To do this, you build custom macros—short for macroinstructions—by typing commands
into an editing module.

3. WHAT CAN YOU DO IN VBA?

1. Data Related Tasks

Data related tasks include everyday Excel tasks to cleanup and format data.

 Remove Duplicates – Create a List of Unique Values

 Select or Delete Blank Rows
 Create formulas with macros – Percentage Change Formula
 Find the Last Used cell, row, or column in a sheet
 Apply formatting to raw data exports – Format Copier

2. Workbook Tasks
We can also automate tasks across worksheets and workbooks. This includes things like listing all the
sheets, creating a table of contents, hiding specific sheets, opening and closing workbooks, and
more. Here are some examples covered in the video.

 Table of Contents and TOC Gallery

 Save and Close All Open Workbooks

3. Pivot Table Tasks

Pivot tables are an amazing tool in Excel. They can also be time consuming to create, format, update,
and maintain. Fortunately, we can automate just about every property and action with pivot tables using
VBA macros.

 Show Details Macro

 Automatic Default Number Formatting in Excel Pivot Tables
 Expand and Collapse Entire Pivot Table Fields
 How to Change Date Formatting for Grouped Pivot Table Fields
 The PivotPal Add-in – The entire add-in was built with VBA, and automates many repetitive pivot
table tasks.

4. Userforms & Add-ins

Userforms are windows that open over Excel with interactive controls. They make our spreadsheets
easier for other users to use. The userforms can be created and modified in the VB Editor.Add-ins are
installed on the users computer and usually contain custom ribbon tabs with buttons. This allows other
users to run our macros on any open workbook.

5. Process Automation

We can also automate more complex processes with macros & VBA. This includes creating systems to
create, update, or modify several Excel files. I created many systems like this for forecasting and
budgeting processes. The File Manager allows you to run multiple macros on sets of files.

4. WHAT ARE THE ADVANTAGES AND DISADVANTAGES BY VBA?

VBA advantages
You can automate almost anything you do in Excel. To do so, you write instructions that Excel carries
out. Automating a task by using VBA offers several advantages:
 Excel always executes the task in exactly the same way.
 Excel performs the task much faster than you can do it manually.
 If you’re a good macro programmer, Excel always performs the task without errors
  If you set things up properly, someone who doesn’t know anything about Excel can perform the
task by running the macro.
 You can do things in Excel that are otherwise impossible — which can make you a very popular
person around the office.
 For long, time-consuming tasks, you don’t have to sit in front of your computer and get bored.
Excel does the work while you hang out at the water cooler.

VBA disadvantages
It’s only fair that equal time is given to listing the disadvantages (or potential disadvantages) of VBA:
 You have to know how to write programs in VBA. Fortunately, it’s not as difficult as you might
expect.
 Other people who need to use your VBA programs must have their own copies of Excel. It
would be nice if you could press a button that transforms your Excel/VBA application into a
stand-alone program, but that isn’t possible (and probably never will be).
 Sometimes, things go wrong. In other words, you can’t blindly assume that your VBA program
will always work correctly under all circumstances. Welcome to the world of debugging and, if
others are using your macros, technical support.
 VBA is a moving target. As you know, Microsoft is continually upgrading Excel. Even though
Microsoft puts great effort into compatibility between versions, you may discover that the VBA
code you’ve written doesn’t work properly with older versions or with a future version of Excel.

REFERENCES:

https://www.longdom.org/open-access/system-analysis-and-design-2165-7866.S8-e001.pdf

https://www.roberthalf.com/blog/salaries-and-skills/6-basic-sdlc-methodologies-which-one-is-
best

https://www.excel-easy.com/vba.html

https://corporatefinanceinstitute.com/resources/excel/study/excel-vba/

https://www.investopedia.com/terms/v/visual-basic-for-applications-vba.asp

https://www.dummies.com/software/microsoft-office/excel/advantages-and-disadvantages-of-
excel-vba/