jinx.net
A .Net MVC Web Application Framework

Nowadays .net web
applications
ASP.Net
Base Libraries
Mix’n’Match of code
Generic Application Framework

Notes on structures
Focus on targets or focus on structure?
Project Managers, Developers or Designers

ASP.Net
Where is the standard in <asp:label>?
Code reusability is up to the developers’
willpower
Layer separation is a dream

ASP.Net
file, file, file, file, file, file, file, file, file,
file, file, file, file, file, file, file, file, file,
file, file, file, file, file, file, file, file, file,
file, file, file, file, file, file, file, file, file,
file, file, file, file, file, file, file, file, file,
file, file, file, file, file, file, file, file, file,
file, file, file, file, file, file, file, file, file,
file, file, file, file, file, file, file, file, file,
file, file, file, file, file, file, file, file...
Where is the Logic of the web application?
Split in N² files!

Base Libraries
They help
Where is the bigger picture?
The responsibility remains on the single
developer
The quality is dependent on the Library
Analyst
It is not a standard approach

Mix’n’Match of code
Everyone brings his own experience and
ideas, mixed and stewed
In a non-structured environment bugs are
the legacy of the previous developer
Different standards applied in different
moments: farewell maintainability
Time wasted to do the same thing again and
again. And again...

Generic Application
Framework
Where does the logic reside?
MVC or something similar? quite similar?
maybe similar?
Easy-to-use or Overcomplicated?

Focus on targets or
focus on structure?
Are you committed to the customers’ needs?
Are you investing your time fulfilling the
requirements?
Is the pattern clear?

Project Manager,
Developer and Designer
Project Manager: talks about business
Developer: talks like a geek
Designer: knows about pixels

Project Manager,
Developer and Designer
Are they speaking the same language?
Is this language globally understood in your
team?
Do they understand each other?

Project Manager,
Developer and Designer
Business Vision, cust x;
needs, UML, x = new cust();
Customer cust.save();
Do they
understand each
other?

One Web Application
Three areas of responsibility
Many Languages
=
Technical Inferno!

These are the problems!

jinx them!

What is jinx.Net?
A strong Model-View-Controller framework
for .Net
A SOA approach to web applications
A method of maintaining a strong separation
among layers
A standard approach to recurrent patterns
...and a vision!

Audience: it is different
Project Managers
Analysts
Developers
Designers

ANOTHER framework?
Based on STANDARDS (no ASP.Net metacode)
Multiple Environment Management: SOA
Data Centric: XML
Multi-View capability: XSLT
Business Logic: Modules
Code Reusability: Components
...visual approach to Analysis & Design!

Wireframe and Site Map
A visual approach that everyone understands
Define the Logic of a web application
Specify the requirements
Immediate

Why not?
Transforming this...
Index
customerList
newCustomer customerDetails
saveCustomer
...into a ready-to-use structure!

Does it sound familiar?

Visual Modeler
Automatic generation of the Model structure
from a sketch, a draw
Maintain applications on targets
No need to “code” the structure
Automatic code generation
Visual impact everyone understands

Everyone in his own role
A visual approach is a common language
Project Managers create the Logic of the
application

Service-Oriented
Architecture
The Business Logic drives the web
application
Centralized common Components
Easy maintenance

“M” means Model
Data, Information
The logic remains visual
Data generation is the center of development
Developers create Information
DTD/XSD boundary between Model and View

“V” means View
User Layout
DTD/XSD boundary between Model and View
Strong built-in XHTML base view
Designers create Views
The Controller applies the correct view to
the data to create the required output

“C” means Controller
application management
The web application is not required to
maintain the environment
The “Visual Model” defines the logic of the
application. The Controller understands.
The controller applies security, business logic
and merges Data and Layout...

Strong Layers
Separation
Data are managed separately from Views
Model and View are synchronized through
data definition (DTD, XSD)
The controller can address different output
of the same data, fulfilling the request of
specific consumers (browser, RSS reader)
Application Design drives the Model and
View, not vice-versa.

Business Logic: Modules
Big web application can be split in small
interoperable modules
Teams can be autonomous
Modules can be reused over and over

Code Reusability:
Components
Code Duplication is Evil!
Data should be required from more than one
page and in more than one module
Components identify specific data, and the
framework makes them available from every
part of the model

Pages or Actions?
Actions are not Views
It’s like GET and POST
You can control the output from the result
of the action

Integrated Data
Persistency
The data-centric model is used for data
sources
No usage of SQL Statements: the
Persistency Manager handles them
Think of Objects, forget the rest

Social Networking?
Reusable Modules...
Why shouldn’t I use your CMS?
Third party modules available for distribution

a NEW framework!
Easy multi-level communication
Strong role identification
Cut down development time
Focus on Target
Module availability and reusability

...those things that don’t kill you make you stronger!
Question, Comments, Critics?
Thank You!