Telelogic Modeling Community: Whitepapers
Our whitepaper library is dedicated to offering information on emerging technologies, assisting in solving a common issue, or features of a particular product and how is relates to industry trends.
| Title |
Net-Centric Operations: Improving Project Development Efforts by Modeling Defense Information Systems |
| Summary |
In this paper, we will explore how an MDD approach can tackle challenges the defense industry faces as it synchronizes an increasingly complex application landscape with shrinking deployment windows and development budgets. |
| Published |
8-May-2008 |
| Download |
Click Here |
| Title |
Achieve Automatic Test Generation Through Software Reuse |
| Summary |
This paper will talk about different forms of reuse, and how they allow you to arrive at an automatic testing process that reduces development costs and increases the overall quality of your final deliverable. |
| Published |
30-Apr-2008 |
| Download |
Click Here 260KB |
| Title |
Model Driven Testing: Your Secret to Survival |
| Summary |
With the emergence of the Unified Modeling Language™ (UML®) standard, software designers now have the means to significantly improve their design productivity by transitioning from a code-based development process to a Model Driven Development™ (MDD™) process. Now, engineers and developers are able to deliver more complex, more intelligent designs in much less time when compared to a code-based development process.
But, software Testing is another case altogether. The Testing process is still largely code-based, and never transitioned to a model-driven process. As a result, this created a serious productivity gap between design and Testing, where complex and intelligent designs can be produced “faster” than our ability to test them. The only way to close this gap is by applying a Model Driven Testing process. |
| Published |
26-Mar-2008 |
| Download |
Click Here |
| Title |
Telelogic System Architect Rapid Deployment Program |
| Summary |
The Telelogic System Architect Rapid Deployment Program (RDP) leverages proven processes, methods and solutions to guide your organization to a successful launch and implementation of your enterprise architecture (EA) program. Because every organization has unique business needs, RDP delivers a well-developed, goal-focused deployment program for enterprise architecture. During the lifecycle of the RDP, Telelogic will be there to assist you. Our team of experts, experienced in deploying Telelogic System Architect®, has helped many organizations leverage its unique capabilities. |
| Published |
25-Mar-2008 |
| Download |
Click Here 141KB |
| Title |
Successful Enterprise Planning through Enterprise Architecture |
| Summary |
To successfully complete a journey, you must first select your destination and then forge a path to it. The journey to a robust, efficient, value-enhancing IT environment is no different. The objective of Enterprise Architecture (EA) is to give the organization the knowledge needed to select the best IT destination and to help ensure that the organization follows the right path to meet its business information goals.
This paper explores the evolution of Enterprise Architecture and its support for successful Enterprise Planning. It also examines how Telelogic System Architect® addresses the current and future requirements of EA activities. |
| Published |
15-Feb-2008 |
| Download |
Click Here 343KB |
| Title |
Enabling Enterprise Business Process Management |
| Summary |
The premise of this paper is that enterprise process modeling, analysis, architecture and implementation are at the core of business process management and optimization. Topics covered include process modeling collaboration considerations, process architectures versus enterprise architectures and the requirements for linkages between the two and process implementation issues. |
| Published |
28-Jan-2008 |
| Download |
Click Here 277KB |
| Title |
Leveraging the Model Driven Development and Software Product Line Engineering Synergy for Success |
| Summary |
Developing software for a portfolio of similar products is a formidable task, but Software Product Line (SPL) engineering practices effectively address this challenge. Model Driven Development™ (MDD™) raises the level of programming abstraction with UML® to make software engineering more efficient. With the Telelogic Rhapsody®/BigLever Software Gears™ Bridge, engineers can now leverage the synergy of the industry’s first integrated MDD and SPL engineering solution, providing a simple, elegant approach that enables organizations to effectively manage product line diversity in MDD for faster development of more new products and features. |
| Published |
24-Jan-2008 |
| Download |
Click Here 516KB |
| Title |
Java State Machines in Telelogic Tau |
| Summary |
Beginning with version 4.0, Telelogic Tau® offers support for state machine diagrams for the generation of Java source code. Java state machines in Tau are implemented in a similar way to those it implements for C++. Note, that in practice, Java and C++ model-based developers rarely generate code for everything in the application. On the contrary, it's more common to use an IDE (such as Eclipse for Java or Visual Studio for C++) to develop the core application, modeling those parts of the application that are "stateful" (i.e., capable of maintaining the status of a process or transaction).
Stateful software is equally common both in desktop and enterprise applications; although, developers often seem to ignore this fact (maybe because they are not used to product support for state machines). |
| Published |
22-Jan-2008 |
| Download |
Click Here |
| Title |
SysML-Based Systems Engineering Using a Model-Driven Development Approach |
| Summary |
For many years, software engineers have successfully applied the UML® to model-based software engineering. There have been several attempts to introduce the UML and the underlying object-oriented methods to systems engineering in order to unify the overall development process. However, many systems engineers continue to use classical structured analysis techniques and artifacts to define system requirements and designs. One reason for this could be that systems engineering is mostly driven by functional requirements. Speaking in terms of system functionality is still considered the most natural way of expressing a design by most of the domain experts involved in the early phases of system development (electrical engineers, mechanical engineers, test engineers, marketing, and, of course, customers). Given this, the only way to unify the overall development process is to extend the UML with regard to function-driven systems engineering and to define a process that enables a seamless transfer of respective artifacts to UML based software engineering. For this purpose, the OMG (Object Management Group) formed the SysML (Systems Modeling Language) consortium.
The following sections describe a SysML-based process that systems engineers can use to capture requirements and specify architecture. The approach uses model execution as a means for requirements verification and validation. |
| Published |
8-Jan-2008 |
| Download |
Click Here 885KB |
| Title |
Optimising Business Alignment and Execution |
| Summary |
- Alignment – what's it all about
- The criticality of requirements
- The role of enterprise architecture
"Organisations must recognise that they are no longer making IT investments – they are investing in IT enabled change in the overall business system."
- John Thorp, The Information Paradox |
| Published |
4-Dec-2007 |
| Download |
Click Here |
<< Prev -
1
2
3
4
5
6
7
8
9
10
- Next >>
|
