14
March

ABIEE™ - SRS for the Client/Consumer - Entry 2

by Matthew Pitts

This is part 2 of series on building the elawyering application ABIEE™. You can find all related entries by selecting "ABIEE" in the category list.

Portion 1: The Software Requirement Specification for client/consumer users of ABIEE™

In entry 1, I roughly outlined most of the features that I envisioned ABIEE™ containing. I also mentioned the size and complexity of the task at hand. Finally, I noted the fact that I would break the development and design process down into manageable chunks. I decided to start the development/design process by outlining the Software Requirement Specifications (SRS) for the client/consumer portion of ABIEE™. You can see a preliminary list of the features for the client in entry 1. The following list is more refined and should be considered the official SRS for the client/consumer portion of ABIEE™. of course this list is also subject to change as the elawyering application development/design process progresses.

Official Software Requirement Specification for the Clients/Consumer Portion of ABIEE™

Pre-Filing Stage

 

  1. Unregistered clients can browse library of resources (RL  SRS Pending)
  2. Clients must register and login for additional features
  3. Clients can organize case related documents that the BKP will need for document generation (BKP SRS Pending). Case related documents include scanned (.pdf or .xps) versions of documents such as bills, tax returns, etc.
  4. clients can view the documents they have uploaded
  5. Clients can send documents to BKP when necessary (BKP SRS Pending)
  6. Clients can build a personal library of resources and use standard methods to manage their library such as add, delete, and sort (RL SRS Pending)
  7. Clients can follow a process checklist which will guide them through the appropriate processes to completion of BK case (intermittently updated as development progresses)
  8. Clients can browse information about BKP such as BKP supplied BIO, experience, etc. on public BKP list)(BKP SRS Pending)
  9. Clients can inquiry/message BKP they are interested in hiring (BKP SRS Pending)
  10. Clients can hire a BKP and complete retainer agreement/service agreement (BKP SRS Pending)
  11. Clients can submit payment to BKP (BKP SRS Pending)
  12. Clients must submit case review/means test to hired BKP (BKP SRS Pending)
  13. Clients can receive case review/means test result from BKP ((BKP SRS Pending)
  14. Clients can receive completed document copies from BKP(BKP SRS Pending)
  15. Clients can inquiry/message BKP they have hired (BKP SRS Pending)
  16. Clients can create reviews for BKPs they have hired (BKP SRS Pending)
  17. Clients can complete questionnaires for later use in document generation.

 

Post-Filing Stage

 

  1. Clients can have case-level calendars updated by BKP (BKP SRS Pending)
  2. Clients can receive standard built-in information about upcoming hearings

 

Note: BKP = Bankruptcy Professional -- RL = Resource Library

 

Published in De Novo

Be sure to read my article in the December 2009 edition of the Washington Young Lawyer's Division publication De Novo. You can read it here.

Sponsors

Thanks for Reading

Matthew A.Pitts

About Matthew A. Pitts

 I am a freelance paralegal in Washington State. I have experience in multiple areas of law in both the private and the public sector. Legal Web Development and Marketing

For the past 7 years I have focused on legal marketing and legal web design and development. I have professional level web programming and design skills.

About this Blog

 The legal service delivery landscape is changing rapidly. Despite the number of options available for legal professionals to establish a web presence and begin to engage in some type of "e-lawyering", there are core fundamentals required for success. In this blog I intend to thoroughly cover these fundamentals. Please subscribe today.

Blog Information

Published by Matthew A. Pitts.
Design by Matthew A. Pitts for Internet Paralegal Innovations™.
Powered by BlogEngine.NET   Icons by Dry Icons
© 2010 All Rights Reserved.