22 february

40
22 February Implementation

Upload: masako

Post on 26-Jan-2016

29 views

Category:

Documents


0 download

DESCRIPTION

22 February. Implementation. Tournament. Good concept Implementation problems Status: terminate or find an alternative that does not require fixed time or location. Software Engineering Elaborated Steps. Concept Requirements Architecture Design Implementation Unit test - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: 22 February

22 February

Implementation

Page 2: 22 February

Tournament

Good concept Implementation problems Status:

terminate or

find an alternative that does not require fixed time or location

Page 3: 22 February

Software Engineering Elaborated Steps

Concept Requirements Architecture Design Implementation Unit test Integration System test Maintenance

Page 4: 22 February

Tools

Version Management Build Systems Integrated Development

Environments

Page 5: 22 February

Version Management

Both during and after development Both code and documentation Uses

Multi-developer change control Releases Support for different environments

Computers Operating systems

Page 6: 22 February

Top Reasons for Using Version Management

Bugs which were fixed reappear

Latest versions of code overwritten by old versions

Which version is the right one? I have so many

I have lost my latest changes

Page 7: 22 February

Questions Addressed Development Issues

How do we integrate parallel work? How do I know which changes were in the code

that was being tested? Who changed this module? When? Why?

Multi-version Issues What versions have been made available to

people? How do I assure that all versions get the changes

that they need? What versions need to be re-released to support

changes made?

Page 8: 22 February

Documentation that Needs Version Control

Manuals: need to reflect the variations of the different releases

Test data: what tests have been run and what was the result

Bug reports Planned changes Any document being edited by

multiple people

Page 9: 22 February

Basic Functions

Ability to add and remove changes Ability to identify differences Record of changes made Storage of different versions Ability to get access to one or more

versions Identification of all the components

needed to build any version

Page 10: 22 February

Need a Baseline

Agreed upon document or code level in large project, formally reviewed and

agreed upon in your project, requires consensus

agreement Basis for further development

in large project, changed only through formal change control procedure

In your project, changed when the developer is “comfortable”

Page 11: 22 February

When To Start Using Version Control

Should you use it during unit testing? What is unit testing? How much structure does your unit

testing require? If unit testing requires significant

infrastructure or scaffolding, it makes sense to start using it very early

Page 12: 22 February

No Special Tools Needed

Identify procedures and data needed to add and remove changes identify differences record changes made store different versions get access to one or more versions build any version

Page 13: 22 February

But there are tools …

CVS: Concurrent Version System Subversion (SVN) SourceForge

Actually uses CVS and SVN, but a different model

Page 14: 22 February

Concurrent Versioning System

Developed in the mid 80s Predecessor RCS (Revision Control

System) Vrije University, Amsterdam

Now open source Until recently, the most commonly

used tool ximbiot.com/cvs/wiki

Page 15: 22 February

What CVS Does Supports hierarchical directories

manages changes on a per file basis Remote repository access

import locally for use Supports parallel development

merges changes identifies, does not resolve, conflicts

Basic tasks getting a working copy committing changes reverting to prior level adding or removing a file synchronizing to the latest code tagging versions of files

Page 16: 22 February

Subversion http://subversion.tigris.org/ improved version of CVS

consistent interfaces except for “compelling reasons”

key changes everything is versioned: directories and file

meta-data as well as files atomic commits

guarantee that all aspects are completed or none are

better performance

Page 17: 22 February

SourceForge Open source development

environment Free web-based facility Purchasable software as well

SourceForge.net supports CVS and SVN Compile farm Trackers Web site

Page 18: 22 February

Lots of Others

Google code TRAC

Page 19: 22 February

Tools

Version Management Build Systems Integrated Development

Environments

Page 20: 22 February

Build System Functions

System configuration Executing

preprocessors compilers linkers

Manage paths and libraries Create executables and libraries

Page 21: 22 February

Types of Build Systems

Platform specific independent

Part of version management systems integrated development

environments nothing (standalone)

Page 22: 22 February

Platform Specific System: Unix make

Uses a makefile Can build full systems or parts Defines dependencies

Simplest example: object file depends on its source file

Executes commands for any (and only) pieces that need to be rebuilt

Page 23: 22 February

Open Source Systems:Lots of Them GNU make

Been around for a while Cons

Built in Perl SCons

Python scripts CMake

cross-platform used in conjunction with the native build

environment Jam

C and C++ See also FT Jam (additional platforms)

Page 24: 22 February

Apache Ant: build +++

http://ant.apache.org Introduction Workflow elements XML-based configuration files Java based

contains features specifically for J2EE

Page 25: 22 February

Ant Control Commands (sample)

Ant: Runs Ant on a supplied buildfile AntCall: Runs another target within the

same buildfile Exec: Executes a system command (can

be OS specific) Java: Executes a Java class Parallel: Forks a new thread for another

Ant tasks Sequential: Grouping of commands Waitfor: Blocks execution until a set of

specified conditions become true

Page 26: 22 February

Tools

Version Management Build Systems Integrated Development

Environments

Page 27: 22 February

Integrated Development Environment What is an IDE?

A programming environment integrated into a software application

Normally includes Source code editor Compiler and or interpreter GUI development tools Build system

May also include Graphical tools (e.g., class hierarchy diagram) Debugger Class browser Version management system

Page 28: 22 February

History

Early programming was not done with IDEs Coding sheets and keypunches Line command make files

Hardware enhancements typewriter-like terminals computer screens

Which of these enabled IDEs? Why?

Page 29: 22 February

Dartmouth Time Sharing System (1964)

Command line system Supported Basic, Algol and FORTRAN DTSS commands:

NEW, OLD, LIST, SAVE, RUN Line starting with number replaced that

line in the current program All other commands implied execution

Considered by most people the first IDE

Page 30: 22 February

Today’s IDEs Menu-driven Proprietary

Microsoft Visual Studio (C#, C++, Visual BASIC) Borland JBuilder (Java) Apple XCode (Mac OS X)

Open Source SharpDevelop (.NET) GNU Emacs (Unix) – major modes for languages

Page 31: 22 February

Eclipse www.eclipse.org Both an IDE and an architecture IDEs

Java, C++, C, C#, Python, PHP, Perl, Smalltalk, CMFL (Coldfusion), Cobol, Fortran, Prolog, Erlang

(you get the idea) IDE built using architecture

Enhancements through plug-ins

Page 32: 22 February

XML

What is it?

Tools

How to use it?

Page 33: 22 February

What is XML?XML - eXtensible Markup Language

A "standard/specification" for describing data with markup tags

Tags can describe data or a structureXML - cornerstone of a set of technologies

XML can be used aloneRelated technologies for most effective use

Page 34: 22 February

History of XML

Built on other technologies GML and SGML – (Standard) Generalized Markup Language: 1960s Before there was Word and WYSIWYG editors

HTML - HyperText Markup Language W3C (World Wide Web Consortium) standard

Page 35: 22 February

.ce Introduction .ju .11 39 .ss The work of authors, publishers, and researchers involves, in varying degrees, three recognizable text Formatting commands: .ce center next line .ju justify right margin .ll line length .ss single spacing

Script Example

Page 36: 22 February

Tags

Focus on data description and structureElement -- a pair of tags with contentAttribute -- specific information about an element

Allow creation of XML DialectsSMIL -- for multimedia (RealPlayer Multimedia players) WML -- Wireless WAP-phones XHTML -- XMLized version of HTMLMathML -- for mathematics

HEML -- historical events

Page 37: 22 February

HTML XML Uses <tag> & </tag> style Markup describes text

Focus on presentation Data is text (limited reuse)

(Relatively) fixed set of tags

Loose syntax End tags assumed Nesting errors affect display

Simple and complete Single use - for Web

Uses <tag> & </tag> style Markup describes information

Focus on data structure Data retains meaning

Extensible - can define new tags

Stringent syntax End tags required Element nesting enforced

Uses related technologies Highly reusable documents

Page 38: 22 February

Related Technologies

XML schema (XSD replaced DTD) provides the syntax defines way elements and attributes represented

in a XML document eXtended Stylesheet Language (XSL)

enables data reuse transform XML into other XML HTML format XML for presentation (rendering)

Fonts, size, color, alignment, ... Rules for ordering

Page 39: 22 February

Tools

XML Parser XSL Processor

Lots and lots of them Should you use them?

Page 40: 22 February

How to Use XML Key uses

Separation of changeable decisions Need for multiple forms

Before you invent your own tags, are there relevant ones that you can appropriate?

Use of attributes versus elements continuing discussion