[GM대우]라세티 프리미어 ㅎㅎ

Legacy 2009. 11. 16. 20:25
 

응모는 여기를 통해서..
http://www.style777.com/?t=1&Surl=255877

1년간 라세티와 마티즈가 꽁짜.. ㅎㅎ
전 벌써 응모 했지요.. ㅎㅎ
style 777
:

eclipse + maven plugin 설치

Legacy 2009. 11. 9. 16:56

http://m2eclipse.sonatype.org/installing-m2eclipse.html
자세한 내용은 위 사이트 보시면 쉽게 하실 수 있습니다.

----------- OLD

http://m2eclipse.sonatype.org/update/
--> 또 바뀌었내요..
http://m2eclipse.sonatype.org/sites/m2e

help -> install new software ( 또는 software update ) 에서 plugin 설치 하시면 됩니다.
기존 plugin 과 충돌 나거나 하시면 required 라고 되어 있는 넘만 설치 하셔도 일단은 통과 ^^*

그 이외 maven 설치는 http://maven.apache.org 에서 필요한거 다운 로드 받으셔서 설치 하심 되어요.
몇 가지 local 세팅을 하셔야 하니 참고 하시구요.

 
PATH=apache maven 설치 경로\bin;%PATH%
JAVA_HOME=JDK 설치 경로
:

Shell Redirection

ITWeb/개발일반 2009. 10. 20. 14:20
man bash 하신 후 redirection 부분 참고 하시면 됩니다.

Handle Name Description
0 stdin Standard input
1 stdout Standard output
2 stderr Standard error

아래는 뽑아서 올려 놓은 거랍니다.. :)

REDIRECTION
       Before  a command is executed, its input and output may be redirected using a special notation inter-
       preted by the shell.  Redirection may also be used to open and close files for the current shell exe-
       cution environment.  The following redirection operators may precede or appear anywhere within a sim-
       ple command or may follow a command.  Redirections are processed in the order they appear, from  left
       to right.

       In  the  following descriptions, if the file descriptor number is omitted, and the first character of
       the redirection operator is <, the redirection refers to the standard input (file descriptor 0).   If
       the  first  character of the redirection operator is >, the redirection refers to the standard output
       (file descriptor 1).

       The word following the redirection operator in the following descriptions, unless otherwise noted, is
       subjected  to brace expansion, tilde expansion, parameter expansion, command substitution, arithmetic
       expansion, quote removal, pathname expansion, and word splitting.  If it expands  to  more  than  one
       word, bash reports an error.

       Note that the order of redirections is significant.  For example, the command

              ls > dirlist 2>&1

       directs both standard output and standard error to the file dirlist, while the command

              ls 2>&1 > dirlist

       directs  only the standard output to file dirlist, because the standard error was duplicated as stan-
       dard output before the standard output was redirected to dirlist.

       Bash handles several filenames specially when they are used in redirections, as described in the fol-
       lowing table:

              /dev/fd/fd
                     If fd is a valid integer, file descriptor fd is duplicated.
              /dev/stdin
                     File descriptor 0 is duplicated.
              /dev/stdout
                     File descriptor 1 is duplicated.
              /dev/stderr
                     File descriptor 2 is duplicated.
              /dev/tcp/host/port
                     If  host is a valid hostname or Internet address, and port is an integer port number or
                     service name, bash attempts to open a TCP connection to the corresponding socket.
              /dev/udp/host/port
                     If host is a valid hostname or Internet address, and port is an integer port number  or
                     service name, bash attempts to open a UDP connection to the corresponding socket.

       A failure to open or create a file causes the redirection to fail.

       Redirections  using  file  descriptors  greater than 9 should be used with care, as they may conflict
       with file descriptors the shell uses internally.

   Redirecting Input
       Redirection of input causes the file whose name results from the expansion of word to be  opened  for
       reading on file descriptor n, or the standard input (file descriptor 0) if n is not specified.

       The general format for redirecting input is:

              [n]<word

   Redirecting Output
       Redirection  of output causes the file whose name results from the expansion of word to be opened for
       writing on file descriptor n, or the standard output (file descriptor 1) if n is not  specified.   If
       the file does not exist it is created; if it does exist it is truncated to zero size.

       The general format for redirecting output is:
              [n]>word

       If  the  redirection operator is >, and the noclobber option to the set builtin has been enabled, the
       redirection will fail if the file whose name results from the expansion of word exists and is a regu-
       lar  file.   If  the  redirection  operator is >|, or the redirection operator is > and the noclobber
       option to the set builtin command is not enabled, the redirection is attempted even if the file named
       by word exists.

   Appending Redirected Output
       Redirection  of  output in this fashion causes the file whose name results from the expansion of word
       to be opened for appending on file descriptor n, or the standard output (file descriptor 1) if  n  is
       not specified.  If the file does not exist it is created.

       The general format for appending output is:

              [n]>>word

   Redirecting Standard Output and Standard Error
       Bash allows both the standard output (file descriptor 1) and the standard error output (file descrip-
       tor 2) to be redirected to the file whose name is the expansion of word with this construct.

       There are two formats for redirecting standard output and standard error:

              &>word
       and
              >&word

       Of the two forms, the first is preferred.  This is semantically equivalent to

              >word 2>&1

   Here Documents
       This type of redirection instructs the shell to read input from the current source until a line  con-
       taining only word (with no trailing blanks) is seen.  All of the lines read up to that point are then
       used as the standard input for a command.

       The format of here-documents is:

              <<[-]word
                      here-document
              delimiter

       No parameter expansion, command substitution, arithmetic expansion, or  pathname  expansion  is  per-
       formed  on  word.  If any characters in word are quoted, the delimiter is the result of quote removal
       on word, and the lines in the here-document are not expanded.  If word is unquoted, all lines of  the
       here-document  are  subjected to parameter expansion, command substitution, and arithmetic expansion.
       In the latter case, the character sequence \<newline> is ignored, and \ must be  used  to  quote  the
       characters \, $, and 　?

       If the redirection operator is <<-, then all leading tab characters are stripped from input lines and
       the line containing delimiter.  This allows here-documents within shell scripts to be indented  in  a
       natural fashion.

   Here Strings
       A variant of here documents, the format is:

              <<<word

       The word is expanded and supplied to the command on its standard input.

   Duplicating File Descriptors
       The redirection operator

              [n]<&word

       is  used  to  duplicate  input  file  descriptors.   If  word expands to one or more digits, the file
       descriptor denoted by n is made to be a copy of that file descriptor.  If the digits in word  do  not
       specify  a  file descriptor open for input, a redirection error occurs.  If word evaluates to -, file
       descriptor n is closed.  If n is not specified, the standard input (file descriptor 0) is used.

       The operator

              [n]>&word

       is used similarly to duplicate output file descriptors.  If n is not specified, the  standard  output
       (file descriptor 1) is used.  If the digits in word do not specify a file descriptor open for output,
       a redirection error occurs.  As a special case, if n is omitted, and word does not expand to  one  or
       more digits, the standard output and standard error are redirected as described previously.

   Moving File Descriptors
       The redirection operator

              [n]<&digit-

       moves  the file descriptor digit to file descriptor n, or the standard input (file descriptor 0) if n
       is not specified.  digit is closed after being duplicated to n.

       Similarly, the redirection operator
       [n]>&digit-

       moves the file descriptor digit to file descriptor n, or the standard output (file descriptor 1) if n
       is not specified.

   Opening File Descriptors for Reading and Writing
       The redirection operator

              [n]<>word

       causes the file whose name is the expansion of word to be opened for both reading and writing on file
       descriptor n, or on file descriptor 0 if n is not specified.  If the file does not exist, it is  cre-
       ated.

:

[펌]Software architecture

Legacy 2009. 10. 19. 23:31
원본글 : http://en.wikipedia.org/wiki/Software_architecture
연관글 : http://en.wikipedia.org/wiki/Zachman_Framework


Software architecture

From Wikipedia, the free encyclopedia

Jump to: navigation, search
Software development process
Activities and steps
Requirements · Specification
Architecture · Design
Implementation · Testing
Deployment · Maintenance
Models
Agile · Cleanroom · DSDM
Iterative · RAD  · RUP  · Spiral
Waterfall · XP · Scrum  · Lean
V-Model  · FDD  · TDD
Supporting disciplines
Configuration management
Documentation
Quality assurance (SQA)
Project management
User experience design
Tools
Compiler  · Debugger  · Profiler
GUI designer
Integrated development environment
This box: view • talk

The software architecture of a program or computing system is the structure or structures of the system, which comprise software components, the externally visible properties of those components, and the relationships between them. The term also refers to documentation of a system's software architecture. Documenting software architecture facilitates communication between stakeholders, documents early decisions about high-level design, and allows reuse of design components and patterns between projects.[1]

Contents

[hide]

[edit] Overview

The field of computer science has come across problems associated with complexity since its formation.[2] Earlier problems of complexity were solved by developers by choosing the right data structures, developing algorithms, and by applying the concept of separation of concerns. Although the term “software architecture” is relatively new to the industry, the fundamental principles of the field have been applied sporadically by software engineering pioneers since the mid 1980s. Early attempts to capture and explain software architecture of a system were imprecise and disorganized, often characterized by a set of box-and-line diagrams.[3] During the 1990’s there was a concentrated effort to define and codify fundamental aspects of the discipline. Initial sets of design patterns, styles, best practices, description languages, and formal logic were developed during that time.[who?] The software architecture discipline is centered on the idea of reducing complexity through abstraction and separation of concerns. To date there is still no agreement on the precise definition of the term “software architecture”.[4]

As a maturing discipline with no clear rules on the right way to build a system, designing software architecture is still a mix of art and science. The “art” aspect of software architecture is because a commercial software system supports some aspect of a business or a mission. How a system supports key business drivers is described via scenarios as non-functional requirements of a system, also known as quality attributes, determine how a system will behave.[5] Every system is unique due to the nature of the business drivers it supports, as such the degree of quality attributes exhibited by a system such as fault-tolerance, backward compatibility, extensibility, reliability, maintainability, availability, security, usability, and such other –ilities will vary with each implementation.[5]

To bring a software architecture user's perspective into the software architecture, it can be said that software architecture gives the direction to take steps and do the tasks involved in each such user's speciality area and interest e.g. the stake holders of software systems, the software developer, the software system operational support group, the software maintenance specialists, the deployer, the tester and also the business end user[citation needed]. In this sense software architecture is really the amalgamation of the multiple perspectives a system always embodies. The fact that those several different perspectives can be put together into a software architecture stands as the vindication of the need and justification of creation of software architecture before the software development in a project attains maturity.

[edit] History

The origin of software architecture as a concept was first identified in the research work of Edsger Dijkstra in 1968 and David Parnas in the early 1970s. These scientists emphasized that the structure of a software system matters and getting the structure right is critical. The study of the field increased in popularity since the early 1990s with research work concentrating on architectural styles (patterns), architecture description languages, architecture documentation, and formal methods[6].

Research institutions have played a prominent role in furthering software architecture as a discipline. Mary Shaw and David Garlan of Carnegie Mellon wrote a book titled Software Architecture: Perspectives on an Emerging Discipline in 1996, which brought forward the concepts in Software Architecture, such as components, connectors, styles and so on. The University of California, Irvine's Institute for Software Research's efforts in software architecture research is directed primarily in architectural styles, architecture description languages, and dynamic architectures.

The IEEE 1471: ANSI/IEEE 1471-2000: Recommended Practice for Architecture Description of Software-Intensive Systems is the first formal standard in the area of software architecture, and was adopted in 2007 by ISO as ISO/IEC 42010:2007.

[edit] Software architecture topics

[edit] Architecture description languages

Architecture description languages (ADLs) are used to describe a Software Architecture. Several different ADLs have been developed by different organizations, including AADL (SAE standard), Wright (developed by Carnegie Mellon), Acme (developed by Carnegie Mellon), xADL (developed by UCI), Darwin (developed by Imperial College London), DAOP-ADL (developed by University of Málaga). Common elements of an ADL are component, connector and configuration.

[edit] Views

Software architecture is commonly organized in views[7], which are analogous to the different types of blueprints made in building architecture. Within the ontology established by ANSI/IEEE 1471-2000, views are instances of viewpoints, where a viewpoint exists to describe the architecture in question from the perspective of a given set of stakeholders and their concerns.

Some possible views (actually, viewpoints in the 1471 ontology) are:

  • Functional/logic view
  • Code/module view
  • Development/structural view
  • Concurrency/process/thread view
  • Physical/deployment view
  • User action/feedback view
  • Data view

Several languages for describing software architectures have been devised, but no consensus has yet been reached on which symbol-set and view-system should be adopted. The UML was established as a standard "to model systems (and not just software)," and thus applies to views about software architecture. Others believe that effective development of software relies on understanding unique constraints of each problem, and so universal notations are doomed because each provides a notational bias that necessarily makes the notation useless or dangerous for some set of tasks[citation needed]. They point to the proliferation of programming languages and a succession of failed attempts to impose a single 'universal language' on programmers, as proof that software thrives on diversity and not on standards.

[edit] Architecture frameworks

Frameworks related to the domain of software architecture are:

Other architectures such as the Zachman Framework, DODAF, and TOGAF relate to the field of Enterprise architecture.

[edit] The distinction from detailed design

Software architecture, also described as strategic design, is an activity concerned with global design constraints, such as programming paradigms, architectural styles, component-based software engineering standards, design principles, and law-governed regularities. Detailed design, also described as tactical design, is an activity concerned with local design constraints, such as design patterns, architectural patterns, programming idioms, and refactorings. According to the Intension/Locality Hypothesis[8], the distinction between strategic and tactical design is defined by the Locality Criterion[8], according to which a statement about software design is non-local if and only if a program that satisfies it can be expanded into a program which does not. For example, the Client-Server style is architectural (strategic) because a program that is built by this principle can be expanded into a program which is not client server; for example, by adding peer-to-peer nodes. Or more simply, it is the distinction of the general from the specific.

Architecture is design but not all design is architectural. In practice, the architect is the one who draws the line between software architecture (architectural design) and detailed design (non-architectural design). There aren't rules or guidelines that fit all cases.

[edit] Examples of Architectural Styles / Patterns

There are many common ways of designing computer software modules and their communications, among them:

[edit] See also

[edit] References

  1. ^ Bass, Len; Paul Clements, Rick Kazman (2003). Software Architecture In Practice, Second Edition. Boston: Addison-Wesley. pp. 21–24. ISBN 0-321-15495-9. 
  2. ^ University of Waterloo (2006). "A Very Brief History of Computer Science". http://www.cs.uwaterloo.ca/~shallit/Courses/134/history.html. Retrieved 2006-09-23. 
  3. ^ IEEE Transactions on Software Engineering (2006). "Introduction to the Special Issue on Software Architecture". http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/trans/ts/&toc=comp/trans/ts/1995/04/e4toc.xml&DOI=10.1109/TSE.1995.10003. Retrieved 2006-09-23. 
  4. ^ SEI (2006). "How do you define Software Architecture?". http://www.sei.cmu.edu/architecture/start/definitions.cfm. Retrieved 2006-09-23. 
  5. ^ a b SoftwareArchitectures.com (2006). "Intro to Software Quality Attributes". http://www.softwarearchitectures.com/one/Designing+Architecture/78.aspx. Retrieved 2006-09-23. 
  6. ^ Garlan & Shaw (1994). "An Introduction to Software Architecture". http://www.cs.cmu.edu/afs/cs/project/able/ftp/intro_softarch/intro_softarch.pdf. Retrieved 2006-09-25. 
  7. ^ Clements, Paul; Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Robert Nord, Judith Stafford (2003). Documenting Software Architectures: Views and Beyond. Boston: Addison-Wesley. pp. 13–15. ISBN 0-201-70372-6. 
  8. ^ a b Amnon H. Eden, Rick Kazman (2003). "Architecture Design Implementation". http://www.eden-study.org/articles/2003/icse03.pdf. 

[edit] Further reading

[edit] External links

:

Playing at W Hotel - 2

Legacy 2009. 10. 19. 22:22
추석 맞이 W 에서 놀아 보기..
인터나 다른데랑 다르게 객실 엘리베이트 올라 갈라면 방키를 넣어야 올라 갈수 있더군요.. ㅋ
대표적인.. 화장실 셀카..
접니다... 근데 좀 엉성하내요.. ㅋ


SANY0627

SANY0630

SANY0631

SANY0627 작성자 jjeong

누구나 이 사진을 볼 수 있습니다 All rights reserved

2009년 10월 11일에 업로드

0 덧글

SANY0630 작성자 jjeong

누구나 이 사진을 볼 수 있습니다 All rights reserved

2009년 10월 11일에 업로드

0 덧글

SANY0631 작성자 jjeong

누구나 이 사진을 볼 수 있습니다 All rights reserved

2009년 10월 11일에 업로드

0 덧글

SANY0633

SANY0635

SANY0636

SANY0633 작성자 jjeong

누구나 이 사진을 볼 수 있습니다 All rights reserved

2009년 10월 11일에 업로드

0 덧글

SANY0635 작성자 jjeong

누구나 이 사진을 볼 수 있습니다 All rights reserved

2009년 10월 11일에 업로드

0 덧글

SANY0636 작성자 jjeong

누구나 이 사진을 볼 수 있습니다 All rights reserved

2009년 10월 11일에 업로드

0 덧글

SANY0637

SANY0638

  

SANY0637 작성자 jjeong

누구나 이 사진을 볼 수 있습니다 All rights reserved

2009년 10월 11일에 업로드

0 덧글

SANY0638 작성자 jjeong

누구나 이 사진을 볼 수 있습니다 All rights reserved

2009년 10월 11일에 업로드

0 덧글


:
◀ PREV : [1] : [···] : [248] : [249] : [250] : [251] : [252] : [253] : [254] : [···] : [317] : NEXT ▶

티스토리툴바