Current MS Students/Florencio Almirol/CS 590

From CSWiki

Jump to: navigation, search

Contents

[edit] Week 1 (06/23/07)

Read Grading and Week 1 of class page. Although ColdFusion isn't open source, I would like to do my class presentation and project on Fusebox 5.1, a ColdFusion framework that IS open source. The ColdFusion application server developer edition can be used on a localhost and 2 other IP addresses. Allowing "users to define their own forms and to specify validation and consistency checks without having to write code *" in my project sounds interesting, useful, and challenging.

Not enough online documentation of Fusebox 5.1 for a project so I ordered Fusebox 5 & FLiP: Master-Class ColdFusion Applications.

Browsed through completed and current MS projects. I'm also interested in Web Services.

[edit] Week 2 (06/30/07)

Read new Fusebox site, joined Fusebox 5 mailing list, and did Fusebox 4 beginning tutorials. Read about Sean Corfield, prolific architect of Fusebox 5.

Went through a sample ColdFusion application (Appendix F in Fusebox 5 & FLiP) with no framework and its corresponding code in Fusebox 5.0.

Listened to class presentations about JESS and Xerces.

[edit] Week 3 (07/07/07)

Preparing Fusebox 5.1 PowerPoint presentation and beginning tutorial for next week. Read Fusebox online documentation. Tutorials are for previous versions of Fusebox. Converting a useful 4.1 tutorial to 5.1 is a challenge. The 5.1 application skeleton now separates the circuits into folders of Model, View, and Controller.

Read class presentations on Struts and OpenCV.

[edit] Week 4 (07/14/07)

Read chapters 1-8 and 14 in Fusebox 5 & FLiP. Presented Fusebox PowerPoint (Media:Fusebox.ppt) and explained corresponding sample code.

Concepts using the electrical fusebox idiom:

Fuse
File, page, or template (e.g. act_login.cfm, qry_users.cfm, dsp_welcome.cfm)
Fuseaction
Task that uses the above files (e.g. <fuseaction name="Welcome">)
Circuit
Tasks of related functionality (i.e. use case) (e.g. "ShoppingCart" or "Checkout") in circuit.xml
Fusebox
Application that is hierarchically organized by functionality in fusebox.xml. All HTTP requests are routed to a single point of entry (e.g. index.cfm for ColdFusion).
Exit Fuseaction (Xfa)
Parameterized point of exit in a web page (e.g. <form name="form1" method="POST" action="#request.myself#=#Xfa.SubmitForm#">)


Correction on dsp_Welcome.cfm
Other users include:
<Cfloop query="getusers"> 

  <cfif Username IS NOT Session.MM_username>
     #Username#
  </cfif>

</Cfloop>

[edit] Week 5 (07/21/07)

Worked on prospectus and read UML 2.0 component diagram articles.

[edit] Week 6 (07/28/07)

I'm considering implementing this application in C# instead of ColdFusion because

  1. .NET is used in more shops than CF, and would be a more useful learning experience.
  2. CF lacks advanced object-oriented features compared to .NET.

However, I will need to learn C#.

[edit] Week 7 (08/04/07)

I answered several questions from Dr. Abbott about Online Catalog.

Unfortunately, the Online Catalog project didn't work out. As Dr. Abbott recommended, I will now pursue the CoolStateLA project. Professor Beaupre's description of the project sounded interesting and challenging.

[edit] Week 8 (08/11/07)

I will meet with Professor Beaupre on Monday, 8/6/07.

  1. Discussed and read an overview of the CoolStateLA Online Portal - Website, News Room, Blogs, Web Cams, News Feeds, Text Feeds, Internet Radio, and List Serv. Professor Beaupre suggested that we need a "syndication engine".
  2. I researched "syndication engine" and "aggregator".
  3. Worked on prospectus.
  4. After my class presentation of Syndication Engine, Dr. Abbott commented that CoolStateLA still needs an overarching architecture.

[edit] Week 9 (08/18/07)

  1. Met with Professor Beaupre on Monday, 8/13/07. After Dr. Abbott's advice and my consideration, I told Professor Beaupre that I prefer to work on the CoolStateLA Systems Analysis and Design.
  2. Professor Beaupre talked more about CoolStateLA - current use of FileMaker Pro, and journalism - types of vioce-over.
  3. Reading "Use Case Literacy" by Hadar Ziv (from Dr. Abbott). This is for requirements engineering of CoolStateLA system.
  4. Met with Dr. Abbott, Prof. Beaupre, Sepideh Nazari, Dhaval Joshi, and Mark Luntzel on Saturday, 8/13/07. Discussed the current and future states of the system. Assigned tasks to us. I will write and present use cases for the CoolStateLA Portal by Saturday, 9/1/07. The website and newsroom have higher priorities, but the other projects also need use cases.
  5. I'll also update my prospectus for presentation next week.

[edit] Week 10 (08/25/07)

  1. Comment | I wouldn't promise too much. The most important product will probably be the use cases. Secondly, to the extent that are able to analyze architecture options that will be useful.
  • Does Joomla really make sense?
  • How well does it support the use cases that you come up with?
  • How well does it support the sort of external archiving systems they plan to use?
  • How well does it integrate with what they use now?
  • What sort of top level architecture will allow them to get started with Joomla (or whatever they use for the website) and add pieces as needed?
  • Etc.
  1. Comment | It might be a nice idea for them to install a wiki on their server. You can put your use cases on their wiki. When you are done, they will have it. If they find it useful, they may want to keep it updated. Also, they may find the wiki useful on its own. I think Joomla has a wiki plugin of some sort.
  2. Comment | You should also see what you can find out about "convergent newsrooms."
  3. Comment | Asset manager and Workflow manager are most important.
  4. Does "Ifra" use Workflow manager?
  5. Look into "ClearCase".

[edit] Week 11 (Final 09/01/07)

  1. Graffito looks useful for CoolStateLA framework, but is not yet fully endorsed by Apache.
    1. (R. Abbott) In looking up Graffito, I saw that it was the basis for Jetspeed. I had never heard of either of them. I'm always torn between wanting to use the newest technology and not wanting to commit to something that may be dropped.
    2. I'll look for a framework like Graffito, but one in production instead of beta status. Dan mentioned that incubator status doesn't mean beta, and that Graffito is "hot".
  2. Joomla doesn't support Use Cases (reference), but could do so with Selenium.
  3. Partial CoolStateLA Use Case Diagram

Image:CoolStateLA_Use_Case_Diagram.gif

  • TO DO BY 09/15/07
  1. Complete typical use cases.
  2. Demo of Graffito.
  1. Create CS 599A page to continue project discussion.
  2. Check MS Project written requirements for library submission.
Retrieved from "http://cs.calstatela.edu/wiki/index.php/Current_MS_Students/Florencio_Almirol/CS_590"
Personal tools