Assignment Details

What Is Compon...

paradigm $-$ Goog...

$7$ Phases of the...

use case for clou.

Unit $1-$ Individual Project $(125$ points$)$

Close

Due: Sun, Sep $8$

Printer Friendly Version

Introduction

The concept of the software design paradigm $($see Software Development Paradigms$)$ has evolved along with the methodology and process of software development. In the last century, a specific software design paradigm is mainly driven and supported by a specific type of programming language or paradigm. For example, you may have experienced a nonstructured design paradigm $($which is driven and supported by a nonstructured programming language or paradigm$),$ a modular or structured design paradigm $($which is driven and supported by a modular or structured programming language or paradigm$),$ a functional design paradigm $($which is driven and supported by a functional programming language or paradigm$),$ and an object$-$oriented design paradigm $($which is driven and supported by a functional programming language$).$

After entering the $21$st century, object$-$oriented programming has become the default programming paradigm for most software development. Therefore, the software design paradigm's evolution is mainly influenced by how software is implemented and delivered. For example, there is a so$-$called component$-$based paradigm $($see Component Based Development$),$ which constructs the software through plug$-$and$-$play carefully selected, ready$-$to$-$use components off$-$the$-$shelf $($COTS$)$ software as its components. In more recent years, along with the maturing cloud computing technology, most software has been developed in the so$-$called service$-$based paradigm, which constructs the software as a service. In the service$-$based paradigm, users do not need to complete any installation and maintenance of the software at their computers; rather, users only need to connect to the server where the software functionality is implemented and executed to get all of their needs satisfied, and the results are then delivered directly back to users' computers.

The software design paradigm embodies the results of people's ideas on how to construct programs, combining them into large software systems and formal mechanisms for how those ideas should be expressed. Thus, you can say that a software design paradigm is a model for a class of problems that share a set of common characteristics. Software design paradigms can be subdivided as follows $($Kaisler$,2005)$:

Design patterns

Components

Software architecture

Frameworks

Based on the characteristics of software design paradigms, it is wise to choose a suitable paradigm in the design phase so that both functional and nonfunctional requirements of the targeted software are met $($Eriksson$,2012).$ This step is commonly called the high$-$level design of software. The functional requirements of the software are what the software should do$,$ whereas the nonfunctional requirements of the software are how the software works. Usually, what the software should do