web application development zsolt tóthusers.iit.uni-miskolc.hu/~tothzs/edu/webdev/component... ·...

Component based DevelopmentWeb Application Development

Zsolt Tóth

University of Miskolc

2017

Zsolt Tóth (University of Miskolc) Component based Development 2017 1 / 30

Overview

Table of Contents

1 Overview

2 Interface-based Programming

3 Tools

4 Project Structures


Overview

Software SystemProvide Services

FunctionalNon-Functional

Single UnitLooks LikeCommunicates with OthersIntegrated

ComplexUsually ModularSoftware Architectures

MVCn-TierSOA


Overview

Terms

sub–system A part of the entire system that provide a well–definedfunctionality.

module A development unit that has a well–defined purpose.Modules are identified by their name.

component A module used by another module.artifact A specific version of a module. A module with a version

number.

These terms are slightly different. During the course, we will stick tothese definitions. Do not mix them.


Overview

Modules, ComponentsTests

UnitComponentIntegration

DependenciesBuild processDeployment

Version numbermajor.minor.build.revisionalpha, beta, releasecandidate, commercialdistributionNever use multiple versionof the same module!


Overview

Component

Standalone Development UnitSpecific Functionality

AbstractnessGranularityCommunicates via Interface

Specific TechnologiesJDBC, JPA, myBatisJ2EE, SpringJackson, JAXB

Other ComponentsIntegrateDepend

+ Encapsulate Functionalities+ Simplify Development

StandardizationCategorize ServicesLock Up Technologies

+ Facilitates TestingComponent TestsIntegration Tests

- Difficult to DesignExperience RequiredCostly Decisions

- Obedience to StandardsCode Review


Overview

3rd Party Components

ProsBoxed SolutionsGeneral TasksFaster DevelopmentReusable Components

ConsLearningDepends on Providers

Versions

Bugs!!!Support???

Logginglog4j, log4j2, slf4j

Data AccessJDBC, myBatisJPA, HibernateSpring Data

Data Conversion, MarshallingJAXB,Jackson, gson

TestingJUnitEasyMock, Mockito


Interface-based Programming

Table of Contents

1 Overview


3 Tools




Component Design

Divide and Conquer!

Complex tasks can be brokendownIncrease re–usabilitySimplify tasks

Separate differentprogramming languagetoolstechnologies



Interface–based Programming

Component CommunicationSeparation of

DefinitionImplementation

Decouple ComponentsLoose CouplingExchangeable Components

FacilitatesDesignDevelopmentMaintenance



Interface

Defines expected behaviorreturn typeparametersexceptionsdocumentation

Static TypeVarious ImplementationsAbstractness

/∗ ∗I n t e r f a c e Desc r i p t i on∗ /i n t e r f a c e MoneyExchangeService {

/∗ ∗Method d e t a i l s@param amount . . .@param currency . . .@return . . .@throws . . .∗ /vo id exchange (

Double amount ,Currency

currency )throws

ExchangingException ;}



Abstract Class vs Interface

SimilaritiesDesign ElementsAbstract TypesDefine Behavior

DifferencesFieldsConcrete MethodsMultiple Inheritance

Decision SupportAbstract class if:

Fields are Needed.Constructor is Needed.Concrete Method is Defined

Template Method

Otherwise Interface



Testing Dependencies

Component TestsTested SeparatelyMocking ExternalDependencies

Does the component work prop-erly, if the external dependencieswork expectedly?

Integration TestsTesting with ExternalDependenciesNo MockingTesting in "Real" EnvironmentAssume Everything isAvailable

Does the component works prop-erly in the System?


Tools

Table of Contents

1 Overview


3 Tools



Tools

Tools – Maven

Applicationmvn <goal>Eclipse plugin

Packagingpomjarwar

PropertiesInheritance

Command Line ToolScriptsIntegration

Project Structuresrc

maintest

targetpom.xml

groupId, artifactId,version


Tools

Project Object Model - pom.xmlArtifact Identification

groupId Company orProject Name

artifactId ComponentName

version Version NumberParent ProjectPackagingProperties

Build ConfigurationProject InformationDevelopment Environment

Source Code ManagementIssue TrackerMailing ListsDevelopers

<!−−Custom −−>< j u n i t . vers ion >4.12 </ j u n i t . vers ion >$ { j u n i t . ve rs ion }<!−− B u i l t −i n −−>$ { p r o j e c t . based i r }$ { p r o j e c t . vers ion }


Tools

Maven Build

Source code → SoftwareCommon Task & Fix Steps

CompileClassesComponents

TestingLinkingDistribution

Automation & Toolsmakemaven, gradle, antJenkins CI

1 validate2 compile3 test4 package5 integration-test6 verify7 install8 deploy


Tools

Maven Life-Cycle

Build Steps → GoalsPrevious Steps are RequiredStep Failure = Build FailureConfiguration via Plugins


Tools

Maven Life-Cycle

clean

Remove target directoryvalidate

Check pom.xmlcompile

src/**.java → *.class

test

JUnit (test/**Test.java)Surefire

package

Zip to jar or warintegration-test

JUnit (test/**IT.java)verify

Check Quality Criteriainstall

Copy to Local Repositorydeploy

distributionManagement

Publishing, Sharing


Tools

Maven Dependency Management

Other Component3rd Party LibraryOther Part of the System

Deployed ArtifactStored in RepositoryAutomatic

SearchDownloadAdding to ClassPath

<dependency><groupId >

org . apache . logg ing . l o g 4 j</ groupId >< a r t i f a c t I d >

l o g 4 j</ a r t i f a c t I d ><vers ion >

2 .8 .2</ vers ion >

</dependency>


Tools

Repositories


Tools

Maven Central & Company’s Private Repositories

Maven Central RepositoryKnown Locationwww.maven.org

PublicLibraries

FreeCommon Tasks

Private RepositoryProxyOur Precious ProductsKept in Secret

LANVPN


Tools

Local Repository $HOME/.m2/

Maven ConfigurationsUsed DependenciesKnown Location

repository directorysettings.xmlsecurity-settings.xml

Stored LocallyDownloaded OnceShared Among Projects

repository+--org/apache/logging|+--log4j/log4j-core||+--2.2||\log4j-core-2.2.jar||\log4j-core-2.2.pom||+--2.5||\log4j-core-2.5.jar||\log4j-core-2.5.pom||+--2.6.2||\......


Tools

settings.xml

Developer’s SettingsShared Among ProjectsServer Access

username, passwordEncryptionsecurity-settings.xml

ProfilesBuild SettingsConditions

OSJDK Version

Properties

< s e t t i n g s xmlns=" . . ">< loca lRepos i t o r y / >< in te rac t i veMode / ><usePlug inReg is t ry / >< o f f l i n e / ><pluginGroups / ><servers / >< m i r ro r s / ><prox ies / >< p r o f i l e s / >< a c t i v e P r o f i l e s / >< / s e t t i n g s >


Project Structures

Table of Contents

1 Overview


3 Tools



Project Structures

Project Structures

No Silver Bullet

Depends onCompanyArchitectProject RequirementsCompetenceLazinessetc.

Defined bySoftware ArchitectsSenior Developers

Should be Considered:Functionalities based on

Users / RolesCommercial UnitsReusability

TechnologiesProgramming TechniquesProgramming Languages

Build and Testings


Project Structures

Example Project Structure #1


Project Structures

Example Project Structure #1util

Utility FunctionsLogging ConfigurationDo not Fit Elsewhere

model

Domain ModelLow Level Validation

persist

Data Access ObjectInterfaces

persist-*

DAO ImplementationDepends on Technology

service

Service DefinitionInterfaces

service-impl

Service Implementationcontroller

Entry Point of the ComponentValidate & Sanitize

DiscussionPros and Cons ?Why?


Project Structures



Project Structures


core

Domain ObjectsValidation

Service DefinitionInterfaceException

service

Service ImplementationDAO General Definition

InterfaceException

DAO

Multiple ImplementationsTechnology Dependent

web

Entry Point of ComponentDeployable

DiscussionPros and Cons ?Why?


web application development zsolt tóthusers.iit.uni-miskolc.hu/~tothzs/edu/webdev/component... ·...

Documents