To fulfill these responsibilities, software designers
typically should have the following personal characteristics,
expertise, training, and experience:
Software designers typically should have the following
personal characteristics:
An abstract thinker who is comfortable working with
mid-level abstractions.
Able to perform engineering trade-offs between competing
design decisions.
Able to identify relevant parts of the requirements,
architectures, and their ramifications on the design.
Able to clearly grasp the context of the design within
the software architecture.
Able to comfortably multitask (i.e., perform multiple
design tasks concurrently).
Relatively self-directed, being able to both manage and
(re)prioritize the multiple concurrent and competing
challenges, issues, ambiguities, and contradictions that
necessarily occur during the prduction of the design.
Strong analytical problem solving skills.
Good verbal and written communication skills, and thus
able to document the design and explain it to its diverse
audiences.
Able to follow the endeavor-specific process and know
when to request a deviation.
Able to collaborate and work well with others as a member
of one or more teams.
Software designers typically should have the following
expertise:
Expert practical knowledge of:
Software design tasks, techniques, and tools.
Software design work products including the
corresponding conventions.
Object-oriented concepts such as abstraction,
encapsulation, inheritance, and polymorphism.
Object modeling and state modeling.
Component-based development (CBD) concepts such as
components, component models, component infrastructures,
and interfaces.
Software design patterns.
Software design approaches to meet quality requirements
and architecture mechanisms (e.g., assertions, exception
handling, concurrent processes and threading, real-time
issues, etc.).
Software modeling languages (e.g., UML, OML) including
the ability to create and read the associated
diagrams.
Software modeling tools.
Solid practical knowledge of:
Requirements engineering concepts and techniques.
Relevant requirements.
Software architecture patterns, concepts, and
techniques.
Relevant architectures including physical architecture
and mechanisms.
The programming languages (e.g., Java, C++, C, HTML,
CSS, XML, JavaScript, assembly languages) and technologies
(e.g., J2EE, EJB) to be used to implement the design.
The theory, practice, and tools of software
engineering.
The application domain.
The application development cycle including relevant
phases and milestones.
Relevant quality engineering tasks and techniques.
Model-based testing tasks and techniques.
Design metrics.
Basic practical knowledge of:
Use case modeling.
Configuration identification, configuration control,
and associated configuration management tools.